STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

tempmail.ninja

tempmail.ninja's public homepage, certificate and DNS checked against 31 practices and compared with 33 Webmail & Message Inboxes sites.

Readiness index
83/100

Webmail & Message Inboxes median 64

Ahead of
91%

of measured Webmail & Message Inboxes sites

Practices observed
22/29

2 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:21:52 UTC from one location. How we measure

Readiness by lane

Green: tempmail.ninja. Thin bar: Webmail & Message Inboxes peer median.

Enable

100/100

Peers 60

Harden

68/100

Peers 67

Accelerate

100/100

Peers 54

Recover

0/100

Peers 19

Priority fixes for tempmail.ninja

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Harden

    Framing restricted

    Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

    Why it matters: Without it, another site can load your pages in a hidden frame and trick visitors into clicking buttons (clickjacking).

    What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

    On Cloudflare: Add the header with a response header transform rule.

    76% of Webmail & Message Inboxes peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    Content Security Policy present

    Observed: The homepage response did not include a Content-Security-Policy header.

    What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

    42% of Webmail & Message Inboxes peers do this.

  3. Priority 3 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for tempmail.ninja, so any public certificate authority may issue for it.

    What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

    33% of Webmail & Message Inboxes peers do this.

  4. Priority 4 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

    20% of Webmail & Message Inboxes peers do this.

What tempmail.ninja already does well

Practices fewer than half of Webmail & Message Inboxes peers use.

  • HTTP/3 advertisedHTTP/3 advertised.15% of peers
  • Structured data presentJSON-LD structured data found.24% of peers
  • Reachable over IPv6IPv6 address published.27% of peers

What we saw

Homepage checked
https://tempmail.ninja/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2027-01-03
CDN or edge
Cloudflare
Platform or framework
Nuxt
DNS operators
Cloudflare
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
69 KB, br
Images on homepage
1 (svg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 22

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 2

  • Modern image formats in use
  • Offscreen images lazy-loaded

Own tempmail.ninja?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: tempmail.ninja. This profile covers configuration only.

Compare with other Webmail & Message Inboxes sites