zippydevtoolsNetwork and HTTP
URL Parser
Break a URL into protocol, domain, path, query string, hash, and port for redirect and callback debugging.
- URLs can contain tokens in query strings or fragments. Review values before sharing output.
Split an OAuth callback
Input: https://app.com/callback?code=abc&state=xyz
Output: { "protocol": "https", "origin": "https://app.com", "hostname": "app.com", "port": null, "pathname": "/callback", "search": "?code=abc&state=xyz", "hash": "", "queryParams": [ { "key": "code", "value": "abc" }, { "key": "state", "value": "xyz" } ] }
What is a URL parser for?
It separates a URL into readable parts for debugging callbacks, redirects, broken links, query strings, and fragments.
Do I need to include the protocol?
Yes. Use an absolute URL with protocol, such as https://example.com/path, to avoid ambiguous parsing.
Does the tool decode query strings?
It uses the browser URL parser and shows parameters separated into key/value pairs.
What happens with an invalid URL?
The tool returns an error and you should review protocol, domain, special characters, and encoding.
Is the URL sent to a server?
No. Parsing runs locally in your browser.