xnxx-porno.com

xnxx-porno.com security report

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

57risk

Elevated

Several issues worth triaging this week.

0Critical

2High

2Medium

2Low

2Info

Collected 6 hours ago16.1sfrom cache

Certificate Transparency1
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication0
Certificate
Security headers6
Archived URLs
Analysis8

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.

Nothing tells receiving mail servers which hosts may send as @xnxx-porno.com, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: xnxx-porno.com
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.xnxx-porno.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@xnxx-porno.com"`, review the reports, then move to p=quarantine and p=reject.
asset: xnxx-porno.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://www.xnxx-porno.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: xnxx-porno.com
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.xnxx-porno.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: xnxx-porno.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: xnxx-porno.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: xnxx-porno.com

final https://www.xnxx-porno.com/status 200time 893msstack cloudflare

✓http:// redirects to https://
!Strict-Transport-Security
max-age=2592000
✓Content-Security-Policy
base-uri 'self';default-src * data: blob: filesystem: about: ws: wss: 'unsafe-inline' 'unsafe-eval'; script-src * data: blob: 'unsafe-inline' 'unsafe-eval';…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
camera=(), microphone=()
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie tb
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
mail.twincdn.com
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
devin.ns.cloudflare.com sharon.ns.cloudflare.com

✓Registered with NameCheap, Inc.15.3 years old
xnxx-porno.com
✓Registration expiry249 days
2027-05-14
✗Transfer lock
none
✓2 nameservers at registry
devin.ns.cloudflare.com sharon.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
104.21.51.90 xnxx-porno.com	80443205220532082208320862087+5	0	Cloudflare~	—
172.67.177.252 xnxx-porno.com +2	80443205220532082208320862087+5	0	Cloudflare~	—

Archived URLs

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