Content & Docs
RFC 8615
Last updated 2026-06-20 · benchmark measured 2026-07-31 — deterministic & reproducible
RFC 8615 defines the /.well-known/ path prefix for well-known URI locations.
75/100
Legit Benchmark — the simple average of 7 measured frames. Frames we could not measure are left out of the average, never counted as zero. Every frame is shown below with its evidence.
Is RFC 8615 production-ready?
Legit.Show scores RFC 8615 75 out of 100 — the simple average of its 7 measured frames. Legit.Show ran its deterministic 7-Frame production-readiness benchmark on RFC 8615 (public-surface assessment), measured from the public surface with no LLM in the scoring path. Its strongest frame is Accessibility; its weakest is Privacy. Every frame it averages is published with its evidence on the Legit.Show listing.
The 7 Frames
- Performance — 99/100
- Accessibility — 100/100
- Security — 25/100
- Privacy — 25/100
- Reliability — 100/100
- Standards — 92/100
- Discoverability — 85/100
What we measured
- No Content-Security-Policy and no HSTS.
- Served over HTTPS with a valid certificate.
- Real Lighthouse performance run — 126 ms to first byte.
- Returns a proper 404 for unknown routes.
- 3 of 3 sampled routes reachable.
- No privacy policy found.
- Sets cookies / loads scripts with no consent prompt.
- Discoverable: sitemap, OpenGraph image, canonical URL.
Who it's for
Web developers · Standards implementers · API designers · System administrators