About this url parser
Inspect the parts of an HTTP or HTTPS URL without visiting it. A URL is parsed locally into scheme, hostname, port, path, query and fragment. The browser URL parser normalizes the address. Use this workspace to prepare a result you can review before putting it to use. All processing takes place on your device, without an account or an upload of your inputs. Check the examples to understand the expected output, read the limitations for the supported scope, and reset the form when you want to start a separate task.
How the url parser works
A URL is parsed locally into scheme, hostname, port, path, query and fragment. The browser URL parser normalizes the address.
URL Parser examples
https://example.com/a?q=1#top
Host: example.com; Path: /a; Query: ?q=1; Fragment: #top
http://example.com:8080/
Scheme: http:; Port: 8080
Limitations & privacy
Only HTTP(S) links up to 2,048 characters are supported. Embedded credentials are rejected. No DNS lookup, request or safety assessment is performed.
Inputs and results stay in this browser. Only tool identifiers are stored for your recently used tools. You can clear that history from the directory.
URL Parser: frequently asked questions
How does the url parser work?
A URL is parsed locally into scheme, hostname, port, path, query and fragment. The browser URL parser normalizes the address.
What can I inspect in the url parser result?
The query parameters in order helps you check the result before using it. Only HTTP(S) links up to 2,048 characters are supported. Embedded credentials are rejected. No DNS lookup, request or safety assessment is performed.
Does the url parser upload my input?
Processing happens in your browser. No tool input or output is uploaded to a server. Use Reset to clear the current workspace before starting a separate task.
Updated September 20, 2026