UtilitySansar
Developer

URL Parser

Paste any URL and instantly see its protocol, host, port, path segments, query parameters, and fragment — with values URL-decoded and ready to copy.

Riepilogo dello strumento

Questo strumento accetta input strutturati e restituisce output deterministici nel browser, senza upload al server.

Nome dello strumento
URL Parser
Intento dell'input
Fornisci il contenuto di origine da trasformare, validare o analizzare.
Intento dell'output
Ricevi un output normalizzato adatto a copia, riutilizzo o debug.
Esempio di input
https://example.com:8443/blog/post-1?utm_source=email&ref=newsletter#share
Esempio di output
protocol: https host: example.com:8443 path: /blog/post-1 query: utm_source=email, ref=newsletter hash: #share

URL components

Protocol
https
Origin
https://shop.example.com:8443
Hostname
shop.example.com
Port
8443
Path
/products/widget
Hash
#reviews

Path segments (2)

  1. 1products
  2. 2widget

Query parameters (3)

KeyValueActions
utm_sourceemail
utm_campaignspring sale
refnewsletter

JSON view

Introduzione allo strumento

Paste any URL and instantly see its protocol, host, port, path segments, query parameters, and fragment — with values URL-decoded and ready to copy.

Panoramica dello strumento

Most URLs hide a lot of structure: subdomains, ports, encoded path segments, repeated query keys, and a fragment that may itself contain key/value pairs. This tool runs your input through the standard WHATWG URL parser, then expands every part into a labelled, copyable view. Query parameters are listed in the order they appear, with their values URL-decoded. Path segments are split on / and decoded too. A read-only JSON view makes it easy to drop the parsed result into a script or test fixture.

Casi d'uso

  • Debug redirects and tracking URLs by inspecting every UTM and query parameter.
  • Extract a deep link’s path segments to validate a route in your app.
  • Convert a stringy URL into a structured object for a test fixture.

Esempi di input/output

Intento dell'input
https://example.com:8443/blog/post-1?utm_source=email&ref=newsletter#share
Intento dell'output
protocol: https
host: example.com:8443
path: /blog/post-1
query: utm_source=email, ref=newsletter
hash: #share

FAQ

What if my URL is missing the scheme?+
The parser requires a scheme. If you paste www.example.com without https://, it will report an error. Add the scheme and try again.
Are query values URL-decoded?+
Yes. Values are decoded so you see the human-readable form, but the original encoded value is also shown.
Does it support internationalized domains (IDN)?+
Yes. Unicode hostnames are accepted; if you need to round-trip them through punycode, use the IDN Punycode Converter.

Esplora altri strumenti

Scopri utility correlate nella categoria Developer qui sotto.

Sfoglia tutti gli strumenti Developer

Strumenti correlati

Utility selezionate che potrebbero esserti utili