What this URL parser shows
Paste a URL and press Parse URL (or Enter). The page builds a URL object with the URL API built into your browser, which implements the WHATWG URL Standard, and prints its protocol, hostname, port, pathname, search and hash. Query parameters are listed with URLSearchParams, so each value is shown decoded: %C3%A9 appears as é, a + as a space, and a key that repeats gets one row per occurrence. The parsing runs in your browser; the address is not sent to our server.
Because a real parser does the work, you see the normalised URL rather than your text echoed back. In our tests, HTTPS://Example.COM:443/a/./b/../c d came out as protocol https:, host example.com, port 443 (default) and path /a/c%20d: the scheme and host were lowercased, the default port dropped, the dot segments resolved and the space encoded. An internationalised host such as münchen.de is shown as xn--mnchen-3ya.de, the punycode form that travels in DNS. Text without a scheme gets http:// prepended first, so example.com:8080/path parses as an http URL on port 8080.
The parts of a URL
Take https://shop.example.com:8443/en/products/list?category=shoes&sort=price#reviews. RFC 3986 names the pieces scheme, authority, path, query and fragment; the browser API uses slightly different property names, which this tool shows side by side:
| Part | In the example | What it does | URL API name |
| Scheme | https | How to talk to the server. It decides the default port and whether the connection is encrypted | protocol, shown with its colon as https: |
| Host | shop.example.com | The server's name or IP address. Case-insensitive; IPv6 addresses appear in square brackets | hostname |
| Port | 8443 | Which service on the host. Omitted when it is the scheme's default: 80 for http, 443 for https | port |
| Path | /en/products/list | Which resource on the server. Case-sensitive on most servers | pathname |
| Query | ?category=shoes&sort=price | Key=value pairs separated by &, sent to the server with the request | search, decoded by searchParams |
| Fragment | #reviews | A position inside the page. Handled by the browser and never sent to the server | hash |
A URL may also carry credentials before the host (user:password@). The parser reads them, but this page does not display them; a URL with credentials in it should not be shared in the first place.
Frequently asked questions
Why parse a URL instead of just reading it?
Long URLs hide things. Parsing shows each tracking parameter (utm_source, gclid, fbclid) decoded on its own row, reveals a redirect target buried inside a return_to parameter, exposes double encoding such as %2520 where a single %20 was meant, and shows the normalised host and path that a browser will actually request.
Is the URL sent to your servers?
No. The page uses the URL API built into your browser, and no request carries the address you typed. Like every page on this site, it loads the Ahrefs Web Analytics script, which records the visit, not what you type.
What does the parser change about the URL I entered?
It shows the normalised form defined by the WHATWG URL Standard: the scheme and host are lowercased, a default port (80 for http, 443 for https) is removed, dot segments such as /./ and /../ are resolved, spaces in the path are percent-encoded, and an internationalised host name is converted to punycode. The values in the query table are decoded, so %C3%A9 appears as é and a plus sign as a space.
What happens if the URL has no scheme?
The page prepends http:// before parsing, so example.com/page is read as http://example.com/page. One exception: a bare host name followed by a port, such as localhost:3000/app, looks like a scheme to that check and is parsed as one, with localhost: shown as the protocol. Type the http:// yourself in that case.
Related tool: to build a value that belongs in a query string, use the URL encoder; its page explains why %20 and + both appear here as spaces.