URL Parser
Parse a full URL into protocol, hostname, port, path, query parameters, and fragment with browser-side processing.
Paste one absolute URL to inspect its protocol, hostname, explicit or default port, pathname, raw query string, fragment, and ordered query entries.
This is a structural parser, not a link checker: it never requests the destination and cannot report HTTP status, redirects, ownership, reputation, or page content.
Use an absolute URL
Include the scheme, for example https://example.com/path. A bare domain such as example.com is intentionally rejected by this interface.
Keep the exact query string
Repeated keys, empty values, plus signs, percent escapes, and parameter order can matter during debugging, so paste the URL exactly as observed.
Redact private values
Remove access tokens, signed parameters, email addresses, internal hosts, and session identifiers before pasting a URL into notes or shared output.
Repeated filters
https://example.com/search?tag=web&tag=tools produces two tag rows, making multi-select filters visible during QA.
Encoded campaign value
https://example.com/?utm_campaign=summer%20launch keeps both the raw search string and the decoded parameter value returned by URLSearchParams.
Security boundary
A URL that parses successfully can still redirect, download a file, impersonate a brand, or expose private data. Inspect unknown destinations with an approved security process.
Preserve evidence
Copy the original URL before editing it when investigating a redirect, analytics mismatch, or support report.
Remove credentials
URLs may contain usernames, tokens, order IDs, search terms, or personal data in the path and query. Redact those values before sharing output.
Choose the next check
Use the encoder/decoder for one component, the UTM Builder for campaign tagging, or the Sitemap URL Checker for a pasted sitemap list.
Treating hostname as the registrable domain
The hostname may include subdomains and internationalized encoding. Domain ownership and public-suffix analysis are outside this parser.
Assuming decoded equals harmless
Decoded query values may contain markup, redirects, or secrets. Parsing does not sanitize a value for HTML, SQL, shell, or application use.
Dropping repeated parameters
Converting query entries into a plain object can overwrite earlier values. Keep the ordered rows when repeated keys are meaningful.
Redirect debugging
Break a copied Location target into host, path, query, and fragment before comparing it with the intended route.
Campaign QA
Inspect UTM names and encoded values without opening the campaign destination.
Support triage
Turn a redacted report URL into structured JSON that an engineer can compare with router expectations.
Documentation
Show learners how an absolute URL separates authority, path, query parameters, and a client-side fragment.
Parser versus checker
This page answers how the string is structured. Reachability, TLS, status codes, robots rules, and final redirects require network checks.
Percent encoding
The raw search field keeps the encoded query while parameter values are exposed through browser parsing. Use URL Encoder & Decoder for component-level changes.
Fragment scope
The fragment follows # and is normally handled by the browser; it is not sent as part of a standard HTTP request to the server.
Does this fetch the URL?
No. It only parses the text of the URL with browser-side processing and does not make a network request.
Can it preserve repeated query parameters?
Yes. The output lists URLSearchParams entries in order, so a URL such as ?tag=a&tag=b produces two rows rather than one overwritten value.
Does a successful parse prove the destination is safe?
No. Parsing checks URL structure only. It does not resolve DNS, follow redirects, scan content, detect phishing, or establish that you should trust the host.
Why is a bare domain rejected?
The browser URL constructor needs an absolute URL in this interface. Add a scheme such as https:// before the hostname.
Does this fetch the URL?
No. It only parses the text of the URL with browser-side processing and does not make a network request.
Can it preserve repeated query parameters?
Yes. The output lists URLSearchParams entries in order, so a URL such as ?tag=a&tag=b produces two rows rather than one overwritten value.
Does a successful parse prove the destination is safe?
No. Parsing checks URL structure only. It does not resolve DNS, follow redirects, scan content, detect phishing, or establish that you should trust the host.
Why is a bare domain rejected?
The browser URL constructor needs an absolute URL in this interface. Add a scheme such as https:// before the hostname.
Suggested workflow
URL inspection workflow
Inventory a URL, inspect its structure, then decode or rebuild only the component you intend to change.