manga-sanctuary.com security report

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

45risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

2Medium

3Low

1Info

Collected 7 hours ago10.3sfrom cache

Certificate Transparency2
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture2
Email authentication1
Certificate
Security headers2
Archived URLs
Analysis7

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.

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.manga-sanctuary.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@manga-sanctuary.com"`, review the reports, then move to p=quarantine and p=reject.
asset: manga-sanctuary.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://www.manga-sanctuary.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.manga-sanctuary.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.manga-sanctuary.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.manga-sanctuary.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.manga-sanctuary.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: manga-sanctuary.com

final https://www.manga-sanctuary.com/status 200time 1692msstack cloudflare

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

✗Cookie PHPSESSID
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
mail.crea-serv.fr
✓SPFends in -all
v=spf1 mx a:mail.crea-serv.fr a:ns3110433.ip-37-187-151.eu -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
✓CAA
0 issue "letsencrypt.org"
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dns200.anycast.me ns200.anycast.me

✓Registered with OVH sas22.7 years old
manga-sanctuary.com
✓Registration expiry1593 days
2031-01-17
✓Transfer lock
client delete prohibited, client transfer prohibited
✓2 nameservers at registry
dns200.anycast.me ns200.anycast.me

Address	Ports	CVEs	Edge	Network
37.187.151.166 manga-sanctuary.com +3	80443	0	direct	—

Archived URLs

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

manga-sanctuary.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames