Skip to content
bobob

URL Parser

Break URLs into protocol, host, pathname, query params, hash, origin, clean URL, and a canonical report.

Runs in your browserNothing you type is sent to a server.

Input and result

What you type is kept in this browser only. Reopen to restore your last run.

Use cases

  • Inspect redirects, callback URLs, query parameters, duplicate canonical reasons, and copy a canonical review report.
  • URL Parser for web workflows

Examples

Common input
https://example.com/tools?q=json#top
Inspect redirects, callback URLs, query parameters, duplicate canonical reasons, and copy a canonical review report.
Typical output
protocol, hostname, pathname, clean URL, duplicate signals, and URL canonical report
Use this as a quick sanity check before copying results.
Tracking URL
https://example.com/path?utm_source=newsletter&id=123#details
Separates query parameters, tracking keys, hash fragments, and a copyable canonical report.
Callback URL
https://app.example.com/callback?state=a%20b&code=redacted
Helps inspect encoded callback parameters and report what must be removed before sharing.
Duplicate URL pair
https://example.com/page?utm_source=x https://example.com/page
Use the clean URL and canonical report before deciding whether a duplicate reason is expected or needs cleanup.

Common mistakes

  • URL Parser can still fail when the pasted input shape differs from https://example.com/tools?q=json#top.
  • The output should be reviewed in the target web workflow before reuse.
  • Browser-local processing does not make sensitive production data safe to paste.

Before you copy

  1. 1Compare the output against the original input before copying.
  2. 2Remove secrets, customer data, and one-off environment values.
  3. 3Continue with url-encoder if the result needs another validation step.

Sources

  • RFC 3986 defines where a URL splits

    scheme, authority (userinfo, host, port), path, query and fragment, each with its own delimiter. The fragment after `#` is **never sent to the server** — which is why it never appears in server logs.

    Basis: RFC 3986

  • Your browser and your server can read the same URL differently

    Browsers follow the WHATWG URL Standard, which is more forgiving than RFC 3986 and normalises spaces and non-ASCII for you. So what the address bar shows and what actually goes over the wire, percent-encoded, are not the same string.

    Basis: WHATWG URL Standard

FAQ

Does URL Parser upload my input?

No. This tool runs in your browser unless the privacy badge explicitly says a server route is required.

Can I use this for production secrets?

Avoid pasting sensitive production data into any website. Prefer local test data or redacted payloads.

Why parse a URL before checking status?

Parsing exposes credentials, tracking parameters, hash fragments, and malformed query values before a network request is made.

What makes a URL unsafe to share?

Credentials, tokens, private hostnames, internal paths, one-off callback codes, and fragments should be removed before sharing or submitting.

What should I check for duplicate canonical issues?

Normalize host, scheme, slash, case, query strings, tracking parameters, and hash fragments before comparing the inspected URL with the declared canonical.