necomps.com security report

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

77risk

Critical

Exposed services or known CVEs need attention now.

0Critical

3High

6Medium

4Low

1Info

Collected 58 minutes ago2.0sfrom cache

Certificate Transparency1
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs23
Registration
DNS posture2
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis14

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 172.67.166.100 (necomps.com), which advertise wordpress 5.5.20, php 7.4.33. 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-2024-25117 CVE-2024-5458 CVE-2024-3566 CVE-2022-4900 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 172.67.166.100 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2024-25117 ↗CVE-2024-5458 ↗CVE-2024-3566 ↗CVE-2022-4900 ↗CVE-2013-2220 ↗
asset: 172.67.166.100
Shodan matched these CVEs against the service banners it saw on 104.21.11.158 (necomps.com), which advertise wordpress 5.5.20, php 7.4.33. 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-2024-25117 CVE-2024-5458 CVE-2024-3566 CVE-2022-4900 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 104.21.11.158 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2024-25117 ↗CVE-2024-5458 ↗CVE-2024-3566 ↗CVE-2022-4900 ↗CVE-2013-2220 ↗
asset: 104.21.11.158
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.necomps.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@necomps.com"`, review the reports, then move to p=quarantine and p=reject.
asset: necomps.com
172.67.166.100 (necomps.com) reports wordpress 5.5.20, php 7.4.33. 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: 172.67.166.100
104.21.11.158 (necomps.com) reports wordpress 5.5.20, php 7.4.33. 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: 104.21.11.158
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://necomps.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://necomps.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://necomps.com/
Nothing tells receiving mail servers which hosts may send as @necomps.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: necomps.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://necomps.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://necomps.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: necomps.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: necomps.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: necomps.com

final https://necomps.com/status 200time 362msstack 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
chuck.ns.cloudflare.com lana.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC10.9 years old
necomps.com
!Registration expiry46 days
2026-10-23
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
chuck.ns.cloudflare.com lana.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.67.166.100 necomps.com +2	80443205220822083208620872095+4	6	Cloudflare~	—
104.21.11.158 necomps.com +2	80443205220532082208320862087+3	6	Cloudflare~	—

Archived URLs

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

necomps.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames