crickfree.be security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

81risk

Critical

Exposed services or known CVEs need attention now.

0Critical

3High

7Medium

6Low

2Info

Collected 2 hours ago8.7sfrom cache

Certificate Transparency2
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs3
Registration
DNS posture1
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis18

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteNo registration data: RDAP has no record at this level.

Shodan matched these CVEs against the service banners it saw on 91.224.59.191 (crickfree.be), which advertise openssh 9.2p1, nginx 1.22.1. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2025-23419 CVE-2023-44487
What to do
Confirm the running versions on 91.224.59.191 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗
asset: 91.224.59.191
Nothing tells receiving mail servers which hosts may send as @crickfree.be, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: crickfree.be
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.crickfree.be TXT "v=DMARC1; p=none; rua=mailto:dmarc@crickfree.be"`, review the reports, then move to p=quarantine and p=reject.
asset: crickfree.be
91.224.59.191 (crickfree.be) reports openssh 9.2p1, nginx 1.22.1. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 91.224.59.191
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 91.224.59.191:22
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://crickfree.be/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://crickfree.be/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://crickfree.be/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://crickfree.be/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://crickfree.be/
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://crickfree.be/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://crickfree.be/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://crickfree.be/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://crickfree.be/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://crickfree.be/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: crickfree.be
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: crickfree.be
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: crickfree.be

final https://crickfree.be/status 200time 5232msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
DENY
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie id_reklam
no Secure · no HttpOnly · no SameSite
✗Cookie cas_zobrazeni
no Secure · no HttpOnly · no SameSite
✗Cookie expirace
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
ASPMX.L.GOOGLE.COM
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓1 nameserver

Address	Ports	CVEs	Edge	Network
91.224.59.191 crickfree.be +2	2280443	2	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

crickfree.be security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames