Web Architecture • Published August 14, 2026

Anatomy of a URL: Complete Guide to RFC 3986 Components & Structure

Master the architectural structure of a URL according to RFC 3986. Learn how schemes, hosts, ports, paths, query strings, and fragments work together.

Explore the full anatomy of a URL according to IETF RFC 3986: Scheme, Authority, Subdomain, Port, Path, Query String, and Fragment.

Frequently Asked Questions

Q1. Does the server receive the fragment (#hash) part of a URL?

No. The fragment identifier (#anchor) is processed exclusively by the client browser for document scrolling or client-side SPA routing. It is never sent in HTTP request headers.

Q2. What is the maximum allowed length of a URL?

While RFC 3986 does not specify a strict upper limit, most modern web servers (e.g. Nginx, Apache) and browsers safely support URLs up to 2,048 characters.

Q3. What is the difference between hostname and host?

Hostname contains only the domain or IP address (e.g., example.com), whereas host includes both the hostname and port number if specified (e.g., example.com:8080).