URL Parser

Key concepts

A URL parser splits campaign links, API endpoints, and redirect addresses into protocol, host, port, path, fragment, and query. It uses the browser URL API, so the rules match what the browser understands. The query string is expanded into a key/value table. An empty port is sometimes shown as the scheme’s default port.

A relative path only may be filled in against the page you are viewing. For debugging, always paste an absolute URL. Parsing is local and is not sent to a server. Encoded Hangul queries may appear in the table as the browser-decoded value.

Example

Parsing https://example.com:443/path?a=1&b=hello#section shows protocol https, host example.com, port 443, path /path, hash section, and query rows a=1 and b=hello. A link with UTM gets a separate row per utm key. Duplicate utm keys on an ad link becoming several rows is a signal to clean the campaign sheet. A port filled with a default can differ from the original without meaning the link is wrong—it is only the browser’s interpretation. Parsing a final redirect URL makes it easier to spot intermediate tracking parameters. When trying the same input several times, reset and paste again so it does not mix with the previous output. On a shared computer, clear the field when you finish so the original is not left on the monitor. Closing the browser tab also discards what you just pasted; you do not need to send a delete request to a server. Button names and field titles match the tool at the top of the screen, so you can follow along as you read. If the result is empty, first check that required fields are filled and that an error message is not hidden.

Related: URL encoder · cURL → fetch · Punycode converter