Organizations that keep the Web running

Standards bodies

Web technologies are shaped in open standards groups.

W3C (World Wide Web Consortium)

• Develops specifications such as CSS, WebAuthn, and WebGPU. HTML and DOM are developed principally at WHATWG, with W3C cooperation.
• The Recommendation track includes Working Draft, Candidate Recommendation, and Recommendation stages, with review and implementation experience. Not every document becomes a Recommendation.
• Member organizations, invited experts, and staff contribute to the work, with opportunities for public feedback.

IETF (Internet Engineering Task Force)

• Works on HTTP, TLS, QUIC, DNS, and more, publishing results as RFCs. RFCs also include Informational and Experimental documents; an RFC number alone does not mean Internet Standard.
• Work is organized by working groups; consensus and real-world deployment are key.
• The IESG manages and approves the IETF standards process. The IAB provides architectural oversight and other functions; these are distinct roles.

WHATWG

• Continuously maintains Living Standards including HTML, DOM, and URL. The browser-oriented URL Standard has a different role from IETF specifications of generic URI syntax.
• Engineers from major browsers (Chrome, Firefox, Safari, Edge) collaborate here.

Names and numbers

Hostnames and IP addresses must be unique, so allocation is hierarchical.

ICANN / IANA

• ICANN coordinates unique identifiers, including DNS. It does not centrally control Web content, and country-code TLD registration policies also involve their own registries and communities.
• IANA functions cover DNS root-zone coordination, global IP and AS-number allocation, and protocol registries. They are provided by PTI, an ICANN affiliate.

Regional Internet Registries (RIRs)

• APNIC (Asia Pacific), ARIN (Canada, United States, and parts of the Caribbean), RIPE NCC (Europe, Middle East, and Central Asia), LACNIC (Latin America and parts of the Caribbean), and AFRINIC (Africa).
• RIRs distribute IP space and ASNs, often via national/organizational registries (e.g., JPNIC).

How domains are issued

• You register through a registrar, which in turn writes to the TLD registry.
• A recursive resolver uses its cache and, when needed, follows root, TLD, and domain authoritative servers. It need not contact every level for every lookup.
• Root DNS consists of 13 lettered clusters (A–M) distributed worldwide.

Implementers and operators

Standards matter only when implemented. Browsers and hosting platforms spread the Web in practice.

Browser vendors

• Chrome (Google), Safari (Apple), Firefox (Mozilla), Edge (Microsoft), and others.
• Experimental features may ship behind flags. Specification work and implementation overlap; shipping an experiment does not guarantee standardization.
• Compatibility is checked using Web Platform Tests (WPT) across engines.

Cloud/hosting/CDN

• Cloud providers (AWS, GCP, Azure, etc.) host Web apps and APIs.
• CDNs (Cloudflare, Akamai, Fastly, etc.) accelerate delivery with global caches and edge compute.
• They often handle certificates and newer protocols (HTTP/2, HTTP/3) on your behalf.

Search engines and crawlers

• Google, Bing, and others crawl the Web and index link structures and content.
• robots.txt and sitemap.xml have become standard interfaces for crawlers.

Policy and safety

Security, privacy, and trustworthiness are handled by multiple forums and practices.

Security-related groups

• CA/Browser Forum develops requirements for publicly trusted TLS server certificates and other certificate types. It does not issue all certificates itself.
• Certificate authorities issue certificates, while browser and other root programs decide which authorities to trust. These are separate roles.
• Security researchers and CERTs coordinate vulnerability disclosure and responses.

Privacy and trust trends

• Browsers implement tracking protection and third-party cookie restrictions while standards discuss new APIs.
• DNS over HTTPS/TLS commonly encrypts the client-to-resolver connection; it does not automatically encrypt every step of name resolution.
• Regional regulations (GDPR/CCPA, etc.) influence how Web features are deployed.

Takeaway

The Web stays decentralized: standards bodies define behavior, naming/numbering authorities avoid collisions, vendors and providers implement and operate, and security/privacy forums guide safe use.

Official sources and related reading

W3C / WHATWG / W3C Process / IETF: RFCs / IESG / IANA / RIRs / CA/Browser Forum
DNS root servers / Browsers and Web standards