Legit.Show measured RFC 8615's Security frame at 25/100. No Content-Security-Policy and no HSTS. Served over HTTPS with a valid certificate.

How does Legit.Show measure RFC 8615?

Legit.Show scores seven frames — Performance, Accessibility, Security, Privacy, Reliability, Standards and Discoverability — deterministically from the public surface (URL, HTTP headers, real Lighthouse), with no LLM in the scoring path. See legit.show/methodology.

Content & Docs

RFC 8615

RFC 8615 defines the /.well-known/ path prefix for well-known URI locations.

70/100

7-Frame production-readiness — according to Legit.Show

Is RFC 8615 production-ready?

Legit.Show measured RFC 8615 at 70 out of 100 on its 7-Frame production-readiness benchmark (public-surface assessment). Its strongest frame is Accessibility (100); its weakest is Privacy (0). Every frame is measured deterministically from the public surface — exactly what was observed is shown below.

The 7 Frames

Performance — 85/100
Accessibility — 100/100
Security — 25/100
Privacy — 0/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.
Lighthouse performance score 85/100 (143 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

Visit RFC 8615 → · How this was measured →