madhappy.com security report

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

39risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

5Medium

7Low

1Info

Collected 9 hours ago4.6sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs13
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis13

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.
note1 host was identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.madhappy.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.madhappy.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.madhappy.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.madhappy.com/
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: madhappy.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.madhappy.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.madhappy.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.madhappy.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.madhappy.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.madhappy.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.madhappy.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: madhappy.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: madhappy.com

final https://www.madhappy.com/status 200time 528msstack cloudflare

✓http:// redirects to https://
!Strict-Transport-Security
max-age=7889238
✓Content-Security-Policy
block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests;
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie _shopify_y
no Secure · no HttpOnly · SameSite=lax
✗Cookie _shopify_s
no Secure · no HttpOnly · SameSite=lax
✗Cookie localization
no Secure · no HttpOnly · SameSite=lax
✗Cookie cart_currency
no Secure · no HttpOnly · SameSite=lax
✓Cookie _shopify_essential
Secure · HttpOnly · SameSite=lax
✓Cookie _shopify_analytics
Secure · HttpOnly · SameSite=lax
✓Cookie _shopify_marketing
Secure · HttpOnly · SameSite=lax

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+1
!SPFends in ~all
v=spf1 include:_spf.google.com ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:b0cfcd24c98c4ca68176ae2320f6b492@dmarc-reports.cloudflare.net
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "amazon.com" · 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
princess.ns.cloudflare.com weston.ns.cloudflare.com

✓Registered with NameCheap, Inc.22.5 years old
madhappy.com
✓Registration expiry535 days
2028-02-24
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
princess.ns.cloudflare.com weston.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
23.227.38.65 madhappy.com +3	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.

madhappy.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames