npcdn.net security report

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

90risk

Critical

Exposed services or known CVEs need attention now.

1Critical

3High

6Medium

3Low

1Info

Collected 21 hours ago15.6sfrom cache

Certificate Transparency42
DNS resolution26
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs53
Registration
DNS posture2
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis14

noteFound 42 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.
note3 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 110.74.174.131 (cdn4.npcdn.net), which advertise openssh 8.0, exim 4.99.5, python 3.6.8, flask 2.0.3, mariadb 10.6.27-MariaDB-log. 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-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2026-27205 CVE-2026-15308 CVE-2026-7210 ...and 73 more
What to do
Confirm the running versions on 110.74.174.131 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 110.74.174.131
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 110.74.174.131:3306
A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://npcdn.net/
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.npcdn.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@npcdn.net"`, review the reports, then move to p=quarantine and p=reject.
asset: npcdn.net
110.74.174.131 (cdn4.npcdn.net) reports openssh 8.0, exim 4.99.5, python 3.6.8, flask 2.0.3, mariadb 10.6.27-MariaDB-log. 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: 110.74.174.131
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: 110.74.174.131: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://npcdn.net/
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://npcdn.net/
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://npcdn.net/
Nothing tells receiving mail servers which hosts may send as @npcdn.net, 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: npcdn.net
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://npcdn.net/
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://npcdn.net/
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: npcdn.net
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: npcdn.net

final https://npcdn.net/status 200time 139msstack cloudflare

✗http:// redirects to https://
✗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)
✓2 nameservers
nelly.ns.cloudflare.com ray.ns.cloudflare.com

✓Registered with Web Commerce Communications Limited dba WebNic.cc10.3 years old
npcdn.net
✓Registration expiry240 days
2027-05-05
✓Transfer lock
client delete prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
nelly.ns.cloudflare.com ray.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
110.74.174.131 cdn4.npcdn.net +14	225380110111143443465+14	88	direct	—
104.26.13.39 npcdn.net +7	80443205320822083208620872095+3	0	Cloudflare~	—
172.67.70.9 npcdn.net +10	80443208220832086208720968080+2	0	Cloudflare~	—
104.26.12.39 npcdn.net +7	80443205220822083208620878080+2	0	Cloudflare~	—

Archived URLs

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

npcdn.net security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames