lolstats.com security report

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

53risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

1Low

1Info

Collected 14 hours ago23.6sfrom cache

Certificate Transparency2
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs39
Registration
DNS posture2
Email authentication0
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.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.lolstats.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@lolstats.com"`, review the reports, then move to p=quarantine and p=reject.
asset: lolstats.com
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://lolstats.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://lolstats.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://lolstats.com/
Nothing tells receiving mail servers which hosts may send as @lolstats.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: lolstats.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: lolstats.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: lolstats.com

final https://lolstats.com/status 200time 73msstack cloudflare · Astro v5.7.9

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
–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
coby.ns.cloudflare.com eva.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC19.2 years old
lolstats.com
✓Registration expiry664 days
2028-07-01
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
coby.ns.cloudflare.com eva.ns.cloudflare.com

Address	Ports	Edge	Network
104.26.14.94 lolstats.com +2	80443205220532082208320862087+5	Cloudflare~	—
104.26.15.94 lolstats.com +2	80443205220532082208320862087+5	Cloudflare~	—
172.67.68.244 lolstats.com +1	80443205220532082208320862087+5	Cloudflare~	—

Archived URLs

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

lolstats.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames