emailondeck.com

Readiness by lane

Green: emailondeck.com. Thin bar: Webmail & Message Inboxes peer median.

Priority fixes for emailondeck.com

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   72% of Webmail & Message Inboxes peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   61% of Webmail & Message Inboxes peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.emailondeck.com.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   58% of Webmail & Message Inboxes peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   58% of Webmail & Message Inboxes peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

What emailondeck.com already does well

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

• Structured data presentJSON-LD structured data found.24% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.30% of peers
• CAA records limit who can issue certificatesCAA limits issuance to letsencrypt.org.33% of peers

What we saw

Homepage checked

https://www.emailondeck.com/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-02

DNS operators

DNS Made Easy

Homepage HTML

20 KB, br

Images on homepage

9 (png 6, svg 6, webp 2)

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

Compare with other Webmail & Message Inboxes sites

• libero.it67
• mailo.com58
• pec.it61
• posteo.de66
• yopmail.com66

Webmail & Message Inboxes readiness benchmark