DataHub Tools URL Parser

URL Parser

Local-first

Parse a URL into protocol, host, path, query parameters, hash, and origin.

How this tool actually works

This browser tool passes one absolute URL to the web platform URL parser, then displays its normalized components. Repeated query keys become arrays; the result reflects browser normalization rather than the original byte-for-byte input.

  • Inspect normalized URL components
  • Decode repeated query parameters
  • Export the parsed result as JSON

How to use it

  1. Paste a complete absolute URL, including its scheme.
  2. Run the parser and compare hostname, port, path, query, and fragment.
  3. Check repeated parameters and normalized characters before copying or downloading JSON.
  4. Treat the result as parsing output, not as a URL safety verdict.

Quick example

Example input

https://example.com:443/a/../b?q=a+b&q=%2B#top

Expected result

hostname: example.com
pathname: /b
query.q: ["a b", "+"]
hash: #top

Relative URLs have no base URL here. The browser may normalize default ports, paths, Unicode hostnames, and percent-encoded data.

Best use cases

  • Debug API and redirect URLs.
  • Inspect repeated query parameters.
  • Prepare a normalized URL summary for documentation.

References and scope

The WHATWG URL Standard defines browser parsing and normalization. RFC 3986 describes generic URI syntax; the two models are related but not byte-for-byte identical.

Sources checked July 24, 2026. Specifications and platform behavior can change; verify the sources before formal use.

Known limitations

  • The output includes hostname and port separately, not one host field.
  • A plus sign in the query is decoded as a space by URLSearchParams; %2B becomes a literal plus.
  • The tool does not detect phishing, open redirects, or malicious destinations.

FAQ

Can it parse relative URLs?

No. This page does not provide a base URL, so use a complete absolute URL.

Why did the port disappear?

A browser may omit a scheme's default port, such as 443 for HTTPS, when normalizing the URL.

Are repeated query keys preserved?

Yes. A repeated key is returned as an array in encounter order.

Does a successful parse mean the URL is safe?

No. Syntax parsing does not establish ownership, reputation, or destination safety.

Related Tools

JSON Formatter Format, minify, and inspect JSON in your browser. JSON JSON Validator Validate JSON and find syntax errors quickly. JSON JWT Decoder Decode JWT header and payload locally. JWT Cron Expression Generator Build common cron expressions and explain existing schedules. Cron URL Encoder Decoder Encode or decode URL components and query strings locally in your browser. URLquery string Base64 Encoder Decoder Encode text to Base64 or decode Base64 back to readable text locally. Base64UTF-8 text Unix Timestamp Converter Convert Unix timestamps to readable dates and generate timestamps from date strings. Unix timestampdate UUID Generator Generate random UUID v4 values locally for tests, records, and identifiers. UUID v4 Text Diff Checker Compare two text blocks line by line and highlight added, removed, and changed lines.