Skip to content
English
All tools

Categories

Developer ToolsEncoding & DecodingJSON & DataHash & ChecksumText ToolsDate & TimeNetwork ToolsFile ToolsMarkdown & Diagrams

URL Parser

Paste a URL and see every component separately, with the query parameters decoded in a table.

Processed locally in your browser

The URL is only parsed, never opened. Without a scheme, https:// is assumed.0 chars · 0 lines
The result will appear here.

What is URL Parser?

A URL is made of a scheme (https:), optional credentials, a host, an optional port, a path, a query string and a fragment. This inspector uses the browser’s WHATWG URL parser, the same algorithm that browsers apply, so what you see is how a browser would read the address.

You get the normalized URL, origin, default port, path segments and internationalized host names in both punycode and Unicode form. The query string is listed as a table of names, decoded values and raw values.

How does it work?

  1. Paste a full URL in the input box. If you leave out the scheme, https:// is assumed and a note tells you so.
  2. Read the component list: protocol, host, port, path, query, fragment and origin.
  3. Check the parameters table to see each query parameter decoded, next to its raw encoded form.
  4. Copy the JSON output if you need the components in a script or a bug report.

Common use cases

  • Debugging a redirect or OAuth callback URL whose query parameters look wrong.
  • Checking which host and port a connection string really points to.
  • Spotting credentials embedded in a URL before you share a log or a screenshot.
  • Comparing the punycode form of an internationalized domain with its Unicode display.

Examples

Try this input in the tool above:

Input
https://demo:secret@www.example.com:8443/docs/guide.html?q=hello%20world&lang=fr&tags=a&tags=b#install
Output
{
  "href": "https://demo:***@www.example.com:8443/docs/guide.html?q=hello%20world&lang=fr&tags=a&tags=b#install",
  "protocol": "https:",
  "username": "demo",
  "password": "***",
  "hostname": "www.example.com",
  "port": "8443",
  "origin": "https://www.example.com:8443",
  "pathname": "/docs/guide.html",
  "pathSegments": [
    "docs",
    "guide.html"
  ],
  "search": "?q=hello%20world&lang=fr&tags=a&tags=b",
  "query": {
    "q": "hello world",
    "lang": "fr",
    "tags": [
      "a",
      "b"
    ]
  },
  "hash": "#install"
}

Privacy

URL Parser runs entirely in your browser. The text or files you provide are processed on your device and are not uploaded, logged or stored on our servers.

Limitations

The tool only parses text: it never opens, fetches or resolves the URL, so it cannot tell whether the address exists or is safe.

Frequently asked questions

Why is the password hidden in the results?

Credentials inside a URL (user:password@host) are risky to display and share, so the password is masked and a warning reminds you that such URLs leak secrets in logs and referrers.

What happens if my URL has no https:// prefix?

The parser assumes https:// so that "example.com/path?x=1" still yields a host and a path. The output notes that the scheme was assumed.

What does xn-- mean in a host name?

It marks punycode, the ASCII encoding of an internationalized domain such as münchen.de (xn--mnchen-3ya.de). The tool shows both forms.

Related tools

More tools in Developer Tools →