Practical guide
How to use the url parser
The URL parser separates an absolute URL into components such as scheme, host, port, path, query and fragment. It is useful when debugging redirects, campaign links and application routing.
Good reasons to use it
- Inspect which part of a complex URL contains a value.
- Separate a hostname from path and query data before coding.
- Find fragments or parameters that may be lost during a redirect.
A reliable workflow
- Paste the complete URL, including its scheme.
- Review each parsed component.
- Decode individual query values only when you understand their expected encoding.
How to interpret the result
A parsed URL can still be unsafe, unreachable or non-canonical. Fragments are handled by the browser and are not normally sent in the HTTP request. Repeated query keys may require application-specific parsing.
Frequently asked questions
Why is the fragment not sent to the server?
The part after # is normally interpreted by the browser or client-side application.
Is a URL valid just because it parses?
No. Parsing identifies structure; it does not verify reachability, safety or application rules.