URL inspect
Break a URL into its parts and decode every query parameter, including the ones that are themselves encoded URLs.
?q=blue%20suede%20shoes&utm_source=news%2Bletter&next=https%3A%2F%2Flogin.example.com%2Fsso%3Fr%3D%2Faccount&tags=a%2Cb%2Cc&debug=&page=2
Credentials are in the URL itself, where proxies and access logs will keep them.
Parts come from the same URL parser a browser uses, so the href above is the normalised form that would actually go on the wire. Values are form-decoded — a “+” in the query means a space — and duplicate keys are kept in order rather than collapsed. The rebuilt query re-encodes from the decoded values, so spaces come back as %20.
Long URLs hide things. Tracking parameters, a redirect target buried in a percent-encoded value, a token where a token should not be — none of it is readable while it is a single line of text.
Paste a URL and it is split into scheme, host, port, path, query and fragment, with parameters listed and decoded one per row. Nested encoding is unwrapped, so a `redirect_uri` containing its own query string becomes readable rather than a wall of `%3A%2F%2F`.
What people open it for
- Reading an OAuth redirect and checking its parameters
- Finding what a marketing or tracking URL is actually carrying
- Debugging a query string that has been encoded more than once
In the terminal
tools urlx
Every utility is also a command in the desktop's shell.