Well-Known URIs
The complete IANA Well-Known URI registry listing all registered suffixes under the /.well-known/ path prefix. Each entry includes the URI suffix, a description of its purpose, the authoritative reference (RFC or specification), and its registration status (permanent, provisional, deprecated, or obsoleted). The registry covers a broad range of use cases including OAuth/OpenID discovery, certificate management, IoT protocols, federated social networking, privacy policies, and security disclosure files.
Quick fetch
Stable URL. CORS-enabled. No auth.
curl https://staticdata.dev/v1/well-known-uris.json
Or use as a typed import:
import { wellKnownUris } from "https://staticdata.dev/v1/well-known-uris.ts"
Formats
- JSON 23.7 KB
/v1/well-known-uris.json
min: 20.6 KB · /v1/well-known-uris.min.json
- CSV 15.6 KB
/v1/well-known-uris.csv
- TypeScript 23.9 KB
/v1/well-known-uris.ts
export const wellKnownUris
type WellKnownUri = (typeof wellKnownUris)[number]
Schema
Each record in the dataset has the following shape.
| Field | Type | Description | Example |
|---|---|---|---|
| uri | string | The URI suffix registered under /.well-known/ | security.txt |
| description | string | A concise explanation of the well-known URI's purpose and usage | A standardized file for disclosing security contact information and vulnerability disclosure policies. |
| reference | string | The authoritative RFC number or specification defining the well-known URI | RFC 9116 |
| status | string | Registration status: permanent, provisional, deprecated, or obsoleted | permanent |
Preview
First 10 records.
| uri | description | reference | status |
|---|---|---|---|
| acme-challenge | Used by the ACME protocol for HTTP-01 domain validation challenges when issuing TLS certificates. | RFC 8555, Section 8.3 | permanent |
| agent-card.json | Publishes an Agent Card describing an AI agent's capabilities and endpoints per the Agent2Agent (A2A) protocol. | A2A Protocol Specification | permanent |
| amphtml | Used by the Google AMP cache to signal cache update requests for AMP HTML pages. | Google AMP Cache Update Specification | provisional |
| api-catalog | Provides a machine-readable catalog of APIs available on the host, per the API Catalog RFC. | RFC 9727 | permanent |
| appspecific | A namespace for application-specific well-known resources, using reverse-domain-name sub-paths. | GitHub well-known-uri-appspecific specification | provisional |
| ashrae | Used for BACnet device discovery and configuration per ASHRAE building automation standards. | BACnet Addenda Add-135-2012am | permanent |
| assetlinks.json | Declares digital asset links that associate a web origin with native apps for Android App Links verification. | Google Digital Asset Links Specification | permanent |
| bluejetty | Provisional registration by PopUp Space Systems LLC for its BlueJetty service metadata; see the referenced specification for details. | BlueJetty Well-Known URI Specification | provisional |
| broadband-labels | Provides standardized broadband consumer labels with speed, pricing, and service details as mandated by regulators. | BITAG Broadband Labels Specification | provisional |
| brski | Supports Bootstrapping Remote Secure Key Infrastructures (BRSKI) for zero-touch device onboarding. | RFC 8995 | permanent |
Fetch examples
Drop-in snippets in five languages.
curl -sSL https://staticdata.dev/v1/well-known-uris.json | jq '.[0]' import type { WellKnownUri } from "https://staticdata.dev/v1/well-known-uris.ts";
const res = await fetch("https://staticdata.dev/v1/well-known-uris.min.json");
if (!res.ok) throw new Error(`Fetch failed: ${res.status}`);
const wellKnownUris: WellKnownUri[] = await res.json();
console.log(wellKnownUris[0]); import urllib.request, json
with urllib.request.urlopen("https://staticdata.dev/v1/well-known-uris.min.json") as r:
wellKnownUris = json.load(r)
print(wellKnownUris[0]) package main
import (
"encoding/json"
"fmt"
"net/http"
)
func main() {
resp, err := http.Get("https://staticdata.dev/v1/well-known-uris.min.json")
if err != nil { panic(err) }
defer resp.Body.Close()
var data []map[string]any
if err := json.NewDecoder(resp.Body).Decode(&data); err != nil {
panic(err)
}
fmt.Println(data[0])
} use serde_json::Value;
fn main() -> Result<(), Box<dyn std::error::Error>> {
let body = ureq::get("https://staticdata.dev/v1/well-known-uris.min.json").call()?.into_string()?;
let data: Vec<Value> = serde_json::from_str(&body)?;
println!("{:?}", data.first());
Ok(())
} Sources and methodology
The data is sourced from the IANA Well-Known URI Registry, which is the authoritative registry for all URI suffixes registered under the /.well-known/ path prefix as defined in RFC 8615. This mechanism allows web services to place metadata and service endpoints at predictable, standardized locations without requiring coordination with site owners about specific paths.
The registry distinguishes four registration statuses. Permanent entries are fully standardized, typically backed by an IETF RFC, and are stable for long-term use. Provisional entries are registered but may still be evolving, often backed by a specification outside the IETF (e.g., W3C, industry consortia, or open-source projects). Deprecated entries were once active but have been superseded or withdrawn, and implementers should migrate away from them. Obsoleted entries have been formally retired.
Descriptions in this dataset are concise summaries derived from the referenced specifications; they are not verbatim text from the IANA registry (which does not include a description column). Records are sorted alphabetically by URI suffix. The dataset reflects the registry as of October 2026 and contains 105 entries.
Versioning
URLs under /v1/ are stable: field names and types will not change in a way
that breaks consumers. Values can be corrected or records added when the upstream source
changes; schema-incompatible updates ship under a new version path. See the
well-known-uris changelog for this dataset's history.
Related datasets
More Web datasets
- aria-attributes
- aria-roles
- character-encodings
- csp-directives
- credit-card-types
- dns-record-types
- dom-events
- emoji
- emoji-shortcodes
- html-elements
- html-entities
- html-attributes
- input-types
- http-auth-schemes
- http-cache-directives
- http-content-codings
- http-headers
- http-methods
- http-versions
- iframe-sandbox-tokens
- ip-protocol-numbers
- keyboard-event-codes
- link-relations
- media-type-suffixes
- oauth-grant-types
- ports
- referrer-policies
- ip-special-blocks
- svg-elements
- tcp-flags
- tlds
- tls-cipher-suites
- tls-versions
- uri-schemes