insidenu.com security report

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

29risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

5Low

1Info

Collected 6 hours ago6.0sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture4
Email authentication1
Certificate
Security headers2
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 502). 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.

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://www.insidenu.com/
Nothing tells receiving mail servers which hosts may send as @insidenu.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: insidenu.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://www.insidenu.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://www.insidenu.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://www.insidenu.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://www.insidenu.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: insidenu.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: insidenu.com

final https://www.insidenu.com/status 200time 1206msstack cloudflare · Next.js

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31556952; preload
✓Content-Security-Policy
frame-ancestors https://platform.sbnation.com https://*.sbnation.com https://platform.insidenu.com https://*.insidenu.com 'self'
✓Clickjacking protection
via CSP frame-ancestors
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

!Cookie vmidv1
Secure · no HttpOnly · SameSite=lax
✗Cookie _vm_consent_type
no Secure · no HttpOnly · no SameSite

–No MX records — domain does not receive mail
✗SPF
no record
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:zicaptxt@ag.dmarcian.com;
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1388.awsdns-45.org ns-1620.awsdns-10.co.uk ns-2.awsdns-00.com ns-817.awsdns-38.net

✓Registered with Amazon Registrar, Inc.14.2 years old
insidenu.com
✓Registration expiry280 days
2027-06-15
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1388.awsdns-45.org ns-1620.awsdns-10.co.uk ns-2.awsdns-00.com ns-817.awsdns-38.net

Address	Ports	CVEs	Edge	Network
199.232.193.246 insidenu.com +2	80443	0	direct	—
199.232.197.246 insidenu.com +2	80443	0	direct	—

Archived URLs

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

insidenu.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames