Inspect any URL. See protocol, host, path, query params, and tracking parameters.
Enter a URL above to inspect its components.
A URL packs a lot of information into one line: the protocol, the host, an optional port, the path, the query string, and a fragment. When a link is long, percent-encoded, or stuffed with parameters, reading it by eye is error-prone. This URL parser online takes any full URL and splits it into labeled parts so you can see exactly where a link points and what data it carries.
Paste a URL and the tool lists every component, then breaks the query string down into a table of individual name and value pairs. Each parameter is also classified as regular or tracking: identifiers like utm_source, fbclid, and gclid are flagged so you can tell application data apart from marketing junk at a glance. If any tracking parameters are found, the tool assembles a clean version of the URL with them removed, ready to copy. That makes it useful for debugging redirects and webhooks, checking what an email or ad click actually passes along, or sanitizing a link before you share it.
Parsing uses the browser built-in URL API and runs entirely on your device, so the links you inspect never leave your machine. If you mostly want to strip parameters in bulk, the dedicated tracking parameter stripper handles many URLs at once.
Enter the link in the URL to inspect field, including the scheme such as https://. Partial URLs without a scheme cannot be parsed and will show an error.
The Components card shows the protocol, host, path, and, when present, the port, query, fragment, and any embedded credentials.
The Query parameters table lists each name and value pair and labels it Regular or Tracking so you can spot analytics identifiers immediately.
If tracking parameters were detected, a Clean URL card shows the link with them removed. Click Copy clean URL to grab it.
A URL consists of a scheme or protocol such as https, an optional username and password, a host name, an optional port, a path, an optional query string of name and value pairs after a question mark, and an optional fragment after a hash sign.
The query string is the part of a URL after the question mark. It holds name and value pairs separated by ampersands, for example ?page=2&sort=date, and is how pages receive parameters like search terms, filters, and campaign tags.
The most common reason is a missing scheme. The parser needs a full URL starting with something like https://, so example.com/page on its own will not parse until you add the protocol.
It checks each parameter name against a list of known tracking identifiers, including everything starting with utm_ plus click IDs like fbclid, gclid, and msclkid and analytics tokens like _ga and mkt_tok. Anything else is labeled regular.
The fragment is everything after the # sign. It is handled by the browser rather than sent to the server and usually points to a section within the page or stores client-side state in single-page applications.
No. The tool parses URLs with the browser built-in URL API directly on your device, and nothing is transmitted to a server.
ReSlug short links don't carry tracking junk you didn't add. Branded, clean, trackable on your terms.