Website readiness profile · Snapshot 23 October 2026
mondialrelay.com
mondialrelay.com's public homepage, certificate and DNS checked against 31 practices and compared with 185 Postage & Courier Services sites.
- Readiness index
- 54/100
- Ahead of
- 29%
- Practices observed
- 14/29
- Popularity band
- Top 50K
Postage & Courier Services median 60
of measured Postage & Courier Services sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: mondialrelay.com. Thin bar: Postage & Courier Services peer median.
Enable
49/100
Peers 75
Harden
55/100
Peers 56
Accelerate
63/100
Peers 53
Recover
0/100
Peers 12
Priority fixes for mondialrelay.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
81% of Postage & Courier Services peers do this. Limit: Only the standard location was requested, once, at the time of the check.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
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.
On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
39% of Postage & Courier Services peers do this.
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for mondialrelay.com was p=none, which asks receivers to take no action on failing mail.
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.
52% of Postage & Courier Services peers do this.
Priority 4 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
69% of Postage & Courier Services peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
What mondialrelay.com already does well
Practices fewer than half of Postage & Courier Services peers use.
- security.txt publishedsecurity.txt with a contact found.3.9% of peers
- HTTP/3 advertisedHTTP/3 advertised.22% of peers
- Reachable over IPv6IPv6 address published.31% of peers
What we saw
- Homepage checked
- https://www.mondialrelay.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-05
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- DMARC policy
- p=none
- Homepage HTML
- 56 KB, gzip
- Images on homepage
- 2 (svg 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
Not observed 15
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Content Security Policy present
- Referrer-Policy set
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 14
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- security.txt published
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Reachable over IPv6
- Canonical URL declared
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own mondialrelay.com?
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: mondialrelay.com. This profile covers configuration only.