Home URL parser
URL parser
An address without https is still read, and query names stay in order.
Why this exists
A campaign link or a sign-in address is long, so the host and the query are hard to see.
The parser puts each boundary on its own line and keeps a repeated query in the order it was written.
-
01How to use it
Paste an address and the rows appear at once.
Example fills in an address with a port, a query, and a hash.
-
02What you get
Protocol, host, port, path, hash, origin, user, and password appear only when they are present.
Each query is one line, name then value.
Enteredexample.com:8080
protocol https hostname example.com port 8080 -
03Worth knowing
A space or a leftover percent encoding in the host gets its own sentence.
Any other bad character asks you to look at the whole address again.
Questions
- QDoes the address leave this browser?
- ANo. Splitting finishes in this browser.
- QWhat if https is missing?
- AIf there is no scheme with slashes, https is added.
- QWhat if a query name appears twice?
- AIt becomes two rows, and the first value stays on top.
How this page works it out
Paste an address and this page splits it into protocol, host, port, path, query pairs, and hash. Each query pair is listed as its own key and value, and the hash is the fragment after the # sign.
A port written in the address is shown as that number. If no port is written, the page does not invent one. The path and the hash stay the text that was typed.
The page does not fetch the address. A host that does not answer still splits if the text is a URL. A failed connection does not change the split.
The split runs only in this browser. Nothing is requested from the host you typed, and the address text is not stored off this page.