nafezly.com security report

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

78risk

Critical

Exposed services or known CVEs need attention now.

0Critical

3High

11Medium

5Low

2Info

Collected 17 hours ago2.3sfrom cache

Certificate Transparency58
DNS resolution14
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs46
Registration
DNS posture2
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis21

noteFound 58 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 91.98.164.185 (blog.nafezly.com), which advertise openssh 8.9p1, nginx 1.18.0. 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 CVE-2021-23017 CVE-2021-3618
What to do
Confirm the running versions on 91.98.164.185 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗CVE-2021-23017 ↗CVE-2021-3618 ↗
asset: 91.98.164.185
Shodan matched these CVEs against the service banners it saw on 46.224.31.97 (ai.nafezly.com), which advertise openssh 8.9p1, nginx 1.18.0. 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 CVE-2021-23017 CVE-2021-3618
What to do
Confirm the running versions on 46.224.31.97 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗CVE-2021-23017 ↗CVE-2021-3618 ↗
asset: 46.224.31.97
Shodan matched these CVEs against the service banners it saw on 49.13.198.44 (accept.nafezly.com), which advertise openssh 9.6p1, nginx 1.24.0. 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 49.13.198.44 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: 49.13.198.44
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: 128.140.97.19:22
91.98.164.185 (blog.nafezly.com) reports openssh 8.9p1, nginx 1.18.0. 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.98.164.185
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.98.164.185:22
46.224.31.97 (ai.nafezly.com) reports openssh 8.9p1, nginx 1.18.0. 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: 46.224.31.97
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: 46.224.31.97:22
49.13.198.44 (accept.nafezly.com) reports openssh 9.6p1, nginx 1.24.0. 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: 49.13.198.44
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: 49.13.198.44:22
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://nafezly.com/
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://nafezly.com/
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://nafezly.com/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: nafezly.com
128.140.97.19 (mail.nafezly.com) reports openssh 9.6p1. 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: 128.140.97.19
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 128.140.97.19:25
test.nafezly.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: test.nafezly.com
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://nafezly.com/
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://nafezly.com/
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: nafezly.com
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: nafezly.com

final https://nafezly.com/status 200time 733msstack cloudflare

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

✗Cookie XSRF-TOKEN
no Secure · no HttpOnly · SameSite=lax
✗Cookie nfthly_session
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
mail.nafezly.com
!SPFends in ~all
v=spf1 +mx +a ~all
✓DMARCp=quarantine
v=DMARC1;p=quarantine;rua=mailto:admin@nafezly.com
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
adam.ns.cloudflare.com tara.ns.cloudflare.com

✓Registered with Cloudflare, Inc.7.0 years old
nafezly.com
✓Registration expiry379 days
2027-09-21
✗Transfer lock
none
✓2 nameservers at registry
adam.ns.cloudflare.com tara.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.67.162.155 nafezly.com +5	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.15.124 nafezly.com +6	80443205220532082208320862087+5	0	Cloudflare~	—
128.140.97.19 mail.nafezly.com +1	222580110143443465587+2	0	direct	—
91.98.164.185 blog.nafezly.com +3	22804438443	4	direct	—
46.224.31.97 ai.nafezly.com +2	2280443	4	direct	—
49.13.198.44 accept.nafezly.com +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.

nafezly.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames