Website readiness profile · Snapshot 23 October 2026
feedly.com
feedly.com's public homepage, certificate and DNS checked against 31 practices and compared with 45 Security & Monitoring sites.
- Readiness index
- 86/100
- Ahead of
- 93%
- Practices observed
- 26/31
- Popularity band
- Top 50K
Security & Monitoring median 66
of measured Security & Monitoring sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: feedly.com. Thin bar: Security & Monitoring peer median.
Enable
95/100
Peers 82
Harden
85/100
Peers 58
Accelerate
85/100
Peers 64
Recover
0/100
Peers 9
Priority fixes for feedly.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
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.
42% of Security & Monitoring peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 0 seconds, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
47% of Security & Monitoring peers do this.
Priority 3 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from DigiCert Inc had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
73% of Security & Monitoring peers do this.
Priority 4 · Enable
Reachable over IPv6
Observed: No IPv6 (AAAA) address was published for feedly.com.
What to do: Enable IPv6 at your CDN or host and publish the AAAA record it provides.
On Cloudflare: Cloudflare offers IPv6 compatibility for proxied hostnames; check the setting in Network.
44% of Security & Monitoring peers do this.
What feedly.com already does well
Practices fewer than half of Security & Monitoring peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.2.2% of peers
- security.txt publishedsecurity.txt with a contact found.12% of peers
- CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.18% of peers
What we saw
- Homepage checked
- https://feedly.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2026-11-12
- CDN or edge
- Cloudflare
- Platform or framework
- Next.js
- DNS operators
- Cloudflare
- HSTS
- max-age 180 days
- DMARC policy
- p=reject
- Homepage HTML
- 86 KB, br
- Images on homepage
- 34 (png 90, webp 53, svg 12, jpg 10)
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
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- 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 feedly.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: feedly.com. This profile covers configuration only.