URL Parser
Parse and analyze URL components including protocol, hostname, path, and query parameters
URL Parser
Parse and analyze URL components including protocol, hostname, path, and query parameters
URL Input
Common Examples
Enter a URL to see live analysis results
The seven components of a URL and what each one controls
- Scheme
- Identifies the protocol —
https,http,ftp,ws,mailto. Determines how the browser or client communicates with the server. - Authority (userinfo + host + port)
- The host is the domain name or IP address. Port is optional and defaults to 443 for HTTPS and 80 for HTTP. Userinfo (
user:pass@) appears in some legacy URLs but is discouraged in modern web contexts. - Path
- The slash-separated hierarchy that identifies a specific resource on the host. Path segments may be URL-encoded but are generally kept human-readable for SEO and usability.
- Query string
- Everything after the
?and before the#. Carries key=value pairs separated by&. Values must be percent-encoded if they contain reserved characters. - Fragment
- Everything after the
#. Identifies a section within the document. The fragment is never sent to the server — it's processed entirely by the browser.
Why query parameter order matters (sometimes)
Technically, query parameter order is not significant per the URL specification — servers should treat ?a=1&b=2 and ?b=2&a=1 identically. In practice, many caching layers and CDNs treat them as different cache keys, and some analytics platforms use parameter order to identify campaign sources. If you're building URLs programmatically, standardise the order by sorting keys alphabetically before assembling the query string.
