RFC Editor
RFC Editor
Every internet protocol spec (HTTP, TLS, DNS, SMTP, OAuth) eventually lands here as an RFC.
What It Is
Canonical publication point for finalized RFCs from the IETF, IRTF, IAB, and independent streams. If it's an RFC number, this is the normative text.
Taxonomy
By RFC number · Full-text search · By stream (IETF, IAB, IRTF, ISE, Legacy)
Top-Level Categories
Master Catalog
Sub-Indexes & Guides
The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.
View all bodies →Curated specs from RFC Editor
DNS is the phone book of the internet. Every domain, email MX record, SPF/DKIM TXT record, and service discovery entry depends on it.
The record types (A, MX, TXT, CNAME) you configure in every DNS panel live in this spec. Know what you're setting.
Every URL in your app, API, auth redirect, webhook, or deep link is built on this grammar. Essential for routing, redirects, and OAuth callback validation.
Your servers, load balancers, firewalls, and security groups are all defined in IPv4/CIDR. Know the addressing model.
ISPs and cloud providers are rolling out IPv6 dual-stack. AAAA records, IPv6 CIDR, and dual-stack routing are real concerns.
Every HTTP request your app makes rides on TCP. Understanding TCP helps with latency, timeouts, keep-alives, and connection pooling.
DNS runs over UDP. QUIC and HTTP/3 run over UDP. Media and gaming often use UDP for low-latency delivery.
HTTP/3 runs on QUIC. Modern CDNs and browsers use it by default. It fixes TCP's head-of-line blocking problem for multiplexed requests.
+81 more in specs browser