URL Parser

About URL parser

The URL parser splits a web address into its parts: protocol, hostname, port, path, query string, fragment and each query parameter. It uses the same URL standard that browsers follow, so what you see is how a browser would interpret the address. It is handy when a long tracking link or redirect target is hard to read by eye.

How to use it

1. Type or paste an address into the URL to Parse field. If you leave off the scheme, https:// is added for you.
2. Click Parse URL.
3. Read the URL Components card: Original URL, Protocol, Hostname, Port, Path, Query String and Hash/Fragment.
4. Scan the Query Parameters card for each key and its decoded value.
5. Press the small copy icon beside any field to copy that piece.

An address with a port, repeated parameter and fragment

https://user@example.com:8443/docs/guide?page=2&sort=desc&tag=a&tag=b#install

Protocol https:, hostname example.com, port 8443, path /docs/guide, query string ?page=2&sort=desc&tag=a&tag=b, fragment #install. Parameters: page = 2, sort = desc, tag = b.

When to use it

• Reading a campaign link to see exactly which utm parameters it carries.
• Checking a redirect target or callback address before pasting it into an OAuth app's settings.
• Extracting the hostname and path from a long address for a script or spreadsheet.
• Debugging why an encoded value in a query string does not look the way you expect.

Questions about URL parser

What port is shown when the address has none?

For https it displays 443 and for http it displays 80, the defaults for each. Other schemes with no explicit port show the placeholder (default) instead.

What happens with a parameter that appears twice?

Only the last occurrence is listed in the Query Parameters card, which is why tag shows b in the example. The full Query String field still contains every repetition in its original order.

Are encoded characters decoded?

In the parameter list, yes: percent codes are turned back into characters and a plus sign becomes a space. The Query String field keeps the encoded form exactly as it was written.

Why did my address without https:// still parse?

The tool checks for a scheme followed by two slashes and, if it is missing, prepends https://. So example.com/page is read as a secure address on that host.

Does it show the username and password?

No. Credentials embedded before the host are accepted, and the hostname is parsed correctly, but they are not displayed as a separate field.

Related tools

• SQL formatter/beautifierFormat & beautify your SQL code with ease.
• User agent parserParse details from user agent strings.
• Cron expression parserTranslate cron expressions to plain English and preview next run times.
• JSONPath testerEvaluate JSONPath expressions against a JSON document and inspect every match in your browser.
• Env to JSON converterConvert .env files to JSON and back, with quoting, comment and multiline support.
• HTML minifierMinify your HTML by removing all the unnecessary characters.