hentaicore.net

hentaicore.net security report

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

37risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

5Low

1Info

Collected 4 hours ago19.3sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis9

noteCertificate Transparency did not complete (HTTP 404). 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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://hentaicore.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://hentaicore.net/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: hentaicore.net
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://hentaicore.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://hentaicore.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://hentaicore.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: hentaicore.net
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: hentaicore.net
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: hentaicore.net

final https://hentaicore.net/status 200time 550msstack cloudflare · WordPress 6.6.2

✓http:// redirects to https://
!Strict-Transport-Security
max-age=15552000; includeSubDomains; preload
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
70abb2c3c10d3bc3f58c9eaf5571d57b.hentaicore.net
!SPFends in ~all
v=spf1 +mx +a +ip4:179.43.188.138 ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:2b8f184b844a40f2a66ce5c304a62e23@dmarc-reports.cloudflare.net
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
john.ns.cloudflare.com meera.ns.cloudflare.com

✓Registered with NICENIC INTERNATIONAL GROUP CO., LIMITED14.9 years old
hentaicore.net
!Registration expiry37 days
2026-10-15
✓Transfer lock
client delete prohibited, client transfer prohibited
✓2 nameservers at registry
john.ns.cloudflare.com meera.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
104.21.4.18 hentaicore.net +3	80443205220532082208320862087+5	0	Cloudflare~	—
172.67.131.134 hentaicore.net +1	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.