Well-Known URIs
Standard, agreed-upon paths under /.well-known/.
9 topics in this category.
-
Well-known URIs
RecommendedThe /.well-known/ path prefix is a standardised place to publish site-level metadata. RFC 8615 defines it; IANA keeps the registry of allowed names.
-
/.well-known/change-password
OptionalA standard redirect endpoint that points password managers and users at your real change-password page. Only applicable if the site has user accounts — sites without logins have nothing to point at and should not implement it.
-
/.well-known/openid-configuration
OptionalA JSON discovery document that describes an OpenID Connect provider's endpoints and capabilities. Only required if you are an OIDC identity provider.
-
/.well-known/api-catalog
RecommendedRFC 9727 publishes a machine-readable index of the APIs and resources a host exposes. Served as a Linkset (RFC 9264) JSON document, discoverable via the api-catalog link relation.
-
/.well-known/webfinger
OptionalWebFinger (RFC 7033) resolves an account identifier such as acct:[email protected] to a set of links. The Fediverse uses it to discover ActivityPub actors.
-
/.well-known/apple-app-site-association
OptionalA JSON file that tells iOS, iPadOS and macOS which Apple apps may handle which URLs on your domain. Required for Universal Links and several other Apple features.
-
/.well-known/assetlinks.json
OptionalAndroid's Digital Asset Links file proves that an Android app and a web domain are owned by the same entity. It powers App Links and Smart Lock for Passwords.
-
/.well-known/nodeinfo
OptionalA discovery URI for federated platforms. It returns links to NodeInfo documents that describe the software, version and basic statistics of a server.
-
/.well-known/traffic-advice
OptionalA JSON file that tells private prefetch proxies — most notably Chrome's — whether to send prefetch traffic to your origin, and at what fraction. Optional opt-out / throttle mechanism, provisionally registered with IANA.