URL parser
What this URL parser does
Enter a full URL and see how it decomposes into scheme (http, https, custom deep link), host, path, query, and typically fragment when present. That mental model matters when OAuth libraries disagree about where the state parameter lives, when CDNs rewrite hosts, or when mobile apps register custom schemes alongside universal links.
When to use it
Use it while comparing staging versus production redirect targets, when debugging why analytics drops query params, or when teaching juniors the difference between path segments and query pairs. Chain with URL redirect checker for hop behavior, URL encoder when composing encoded params, and Safe URL checker before visiting unfamiliar destinations surfaced from logs.
Worked example
A payment return URL fails validation. Parsed output shows the gateway appended extra query keys after your fragment—your router never saw them. You move critical params ahead of # or switch to server-side return POST.
Frequently asked questions
Are parsed pieces ready for encoding?
Components may still need percent-encoding when recombined—especially non-ASCII paths and reserved characters in query values.
IPv6 literals?
Hosts like [2001:db8::1] use bracket notation; parsers should preserve them for downstream HTTP clients.
localhost versus 127.0.0.1?
They compare differently in cookies and CORS. Parsing clarifies which literal your bug uses.