Website readiness profile · Snapshot 23 October 2026
driffle.com
driffle.com's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 88/100
- Ahead of
- 99%
- Practices observed
- 26/31
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: driffle.com. Thin bar: E-Commerce & Marketplaces peer median.
Enable
100/100
Peers 86
Harden
75/100
Peers 60
Accelerate
100/100
Peers 69
Recover
0/100
Peers 11
Priority fixes for driffle.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.
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.
32% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
X-Content-Type-Options: nosniff
Observed: The homepage response did not include X-Content-Type-Options: nosniff.
What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
On Cloudflare: Add the header with a response header transform rule.
64% of E-Commerce & Marketplaces peers do this.
Priority 3 · 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.
7.6% of E-Commerce & Marketplaces peers do this.
Priority 4 · Harden
Referrer-Policy set
Observed: The homepage response did not include a Referrer-Policy header.
What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.
20% of E-Commerce & Marketplaces peers do this.
What driffle.com already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.7.7% of peers
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.16% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
What we saw
- Homepage checked
- https://driffle.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-08
- CDN or edge
- Cloudflare
- Platform or framework
- Next.js
- DNS operators
- Cloudflare
- DMARC policy
- p=reject
- Homepage HTML
- 518 KB, br
- Images on homepage
- 85 (webp 41, svg 22, png 4)
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 5
Observed 26
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- 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
Own driffle.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: driffle.com. This profile covers configuration only.