Website readiness profile · Snapshot 23 October 2026
bsky.app
bsky.app's public homepage, certificate and DNS checked against 31 practices and compared with 193 Social Media & Networking sites.
- Readiness index
- 74/100
- Ahead of
- 78%
- Practices observed
- 18/29
- Popularity band
- Top 5K
Social Media & Networking median 63
of measured Social Media & Networking sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: bsky.app. Thin bar: Social Media & Networking peer median.
Enable
79/100
Peers 76
Harden
66/100
Peers 56
Accelerate
87/100
Peers 62
Recover
0/100
Peers 5
Priority fixes for bsky.app
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
86% of Social Media & Networking peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Enable
Page language declared
Observed: The homepage <html> element had no lang attribute.
What to do: Set lang on the html element (for example lang="en") and on any sections in another language.
86% of Social Media & Networking peers do this.
Priority 3 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
35% of Social Media & Networking peers do this.
Priority 4 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 394-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.
60% of Social Media & Networking peers do this.
What bsky.app already does well
Practices fewer than half of Social Media & Networking peers use.
- security.txt publishedsecurity.txt with a contact found.13% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.38% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.39% of peers
What we saw
- Homepage checked
- https://bsky.app/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Amazon, 394-day validity, expiring 2027-02-12
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 28 KB, gzip
- Images on homepage
- 0
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 11
Observed 18
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- Certificate has more than 14 days left
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own bsky.app?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: bsky.app. This profile covers configuration only.