Delimiter.live
Developer Tools Runs in your browser Free · no account

URL Parser

The URL parser breaks a URL into its component parts using the same rules a browser applies: scheme, host, port, path, query parameters and fragment. Nothing is requested — the URL is only taken apart, so parsing a link tells you nothing about whether it resolves.

URL 0 characters
Components

Your result will appear here.

Not sure where to start? Use Load example.

Results update automatically and are calculated on your device. Nothing you type is sent to a server.

Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.

How to use the URL Parser

  1. Paste the full URL, including the scheme — a bare domain cannot be parsed on its own.
  2. Read the components in the results panel.
  3. Use the Query String Parser if you need each parameter value in full.

Example

Input
https://example.com:8443/a/b?x=1#top
Output
Scheme: https
Host: example.com
Port: 8443
Path: /a/b
Fragment: top

Common use cases

  • Working out which part of a long tracking URL is the real destination.
  • Checking the port and scheme on a URL that behaves unexpectedly.
  • Confirming a fragment is present before debugging client-side routing.
  • Extracting the origin from a URL for a CORS allowlist.

Limitations and things to watch for

  • Parsing is not fetching. A URL that parses cleanly may still be dead, and this tool makes no request to find out — use the HTTP Header Checker for that.
  • The scheme is required. Browsers guess when you type a bare domain into the address bar; the URL API does not, and neither does this tool.
  • Internationalised domain names are shown in their Punycode form, because that is how they are actually sent on the wire.

Frequently asked questions

Why does a bare domain fail?
Because example.com is ambiguous — it could be a hostname or a relative path. The URL standard requires a scheme, so include https:// and it will parse. Your browser guesses in the address bar; the parser does not.
Does this tool visit the URL?
No. It only splits the string apart, entirely in your browser. Nothing is requested and nothing is sent anywhere, so you can safely parse a URL containing a token without it being transmitted.
What is the origin?
The scheme, host and port together — the identity a browser uses for same-origin policy decisions. Two URLs share an origin only when all three match, which is why https and http versions of a site are different origins.
Why is the password hidden?
Credentials embedded in a URL are shown masked, because they should not be there in the first place. They travel in plain text and end up in server logs and browser history.

Share this tool