What we check
We fetch the well-known path and require valid JSON with an issuer field.
of 198 sites we could read pass this.
Why it matters
OpenID Connect Discovery 1.0 is a final specification. It's for sites that act as an OpenID provider, and most sites aren't one.
Required fields include issuer, authorization_endpoint, jwks_uri, response_types_supported, subject_types_supported and id_token_signing_alg_values_supported.
How to fix it
- If you use an identity provider, it probably publishes this for you.
- Otherwise, serve the JSON document at the well-known path.
Fix it yourself with AI
Small fixes shouldn't sit in a queue. Give your AI agent one prompt, and it fixes and deploys for you.
PromptShip is made by the team behind this checker.
Sources
Fixed it?
Run your site through the checker, and re-check after you ship to see what improved.
Check my site