Enter URL
Parse Result
History
URL Structure Guide
Learn about URL components and understand the anatomy of Uniform Resource Locators
Complete URL Structure
The complete syntax structure of URLs and meaning of each component
scheme://[userinfo@]host[:port][/path][?query][#fragment]
| Component | Description | Details |
|---|---|---|
|
|
Defines the protocol used to access the resource, such as http, https, ftp, mailto |
Common: http(80), https(443), ftp(21), ws(80), wss(443) |
|
|
Contains user info, hostname, and port number for resource identification |
Format: [userinfo@]host[:port], e.g., user:pass@example.com:8080 |
|
|
Identifies the server by domain name or IP address, the most critical URL part |
Can be domain(example.com), IPv4(192.168.1.1) or IPv6([::1]) |
|
|
Specifies the service port on the server, uses protocol default when omitted |
Range: 1-65535, common defaults: 80(HTTP), 443(HTTPS), 21(FTP) |
|
|
Specifies the exact location of resource on server, similar to filesystem path |
Hierarchical structure with / separators: /docs/guide/installation.html |
|
|
Key-value pairs starting with ? to pass additional information to server |
Format: ?key1=value1&key2=value2, special characters need URL encoding |
|
|
Starting with # for in-page navigation, typically points to specific page sections |
Client-side only, not sent to server, e.g., #section1 |
|
|
Contains username and password for authentication, rarely used in modern apps |
Format: username:password@, not recommended due to security concerns |
|
|
Special characters must be percent-encoded to ensure proper URL transmission |
Space→%20, Chinese→UTF-8 encoding, reserved chars like ?→%3F |
|
|
Path references based on current page location, simplifying URL writing |
./same level, ../parent, /root path, //protocol relative, ?query only |
|
|
Follows RFC 3986 and other international standards for URL uniformity and compatibility |
Max length typically limited to 2048 chars, supports internationalized domain names |