neverssl.com 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.

1Critical

1High

5Medium

4Low

1Info

Collected 23 hours ago26.8sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture4
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis12

noteCertificate Transparency did not complete (HTTP 429). Results below are partial.
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.

Shodan matched these CVEs against the service banners it saw on 34.223.124.45 (neverssl.com), which advertise http server 2.4.66. 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-2026-49975 CVE-2026-48913 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42536 CVE-2026-42535 CVE-2026-34356 CVE-2026-34355 CVE-2026-34059 CVE-2026-34032 CVE-2026-33857 CVE-2026-33523 ...and 21 more
What to do
Confirm the running versions on 34.223.124.45 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-48913 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗
asset: 34.223.124.45
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.neverssl.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@neverssl.com"`, review the reports, then move to p=quarantine and p=reject.
asset: neverssl.com
34.223.124.45 (neverssl.com) reports http server 2.4.66. 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: 34.223.124.45
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://neverssl.com/
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://neverssl.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://neverssl.com/
Nothing tells receiving mail servers which hosts may send as @neverssl.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: neverssl.com
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://neverssl.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://neverssl.com/
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: neverssl.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: neverssl.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: neverssl.com

final https://neverssl.com/status 200time 702msstack cloudflare

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

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓4 nameservers
ns-1413.awsdns-48.org ns-1716.awsdns-22.co.uk ns-320.awsdns-40.com ns-570.awsdns-07.net

✓Registered with Amazon Registrar, Inc.9.9 years old
neverssl.com
!Registration expiry47 days
2026-10-23
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1413.awsdns-48.org ns-1716.awsdns-22.co.uk ns-320.awsdns-40.com ns-570.awsdns-07.net

Address	Ports	CVEs	Edge	Network
34.223.124.45 neverssl.com +1	443	36	direct	—

Archived URLs

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

neverssl.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames