URL Parameter Extractor & Analyzer
Paste any URL and get a complete breakdown — protocol, domain, subdomain, TLD, port, path, file extension, every query and hash parameter, tracking tags, and SEO/security notes. All in your browser, nothing uploaded.
What is a URL, and what can be broken down?
A URL (Uniform Resource Locator) is made up of several distinct parts: a protocol/scheme, an optional username and password, a hostname (with subdomain, domain name and top-level domain), an optional port, a path made of segments, an optional query string of key-value parameters, and an optional hash fragment. This tool parses every one of those parts individually, so instead of staring at one long string you get a clean, labelled breakdown of exactly what a link contains.
Anatomy of a URL
Take https://user:pass@blog.example.co.uk:8443/articles/post.html?utm_source=fb&page=2#section-2 as an example: https is the protocol, user:pass are credentials embedded in the link, blog is the subdomain, example.co.uk is the registrable domain (with example as the domain name and co.uk as the two-part TLD), 8443 is an explicit port, /articles/post.html is the path (with .html as the file extension), utm_source=fb&page=2 is the query string, and #section-2 is the hash fragment.
How to use this URL Parameter Extractor
- Paste a URL into the box above — a full link with
https://, or just the domain and query string. - Click "Extract parameters" to get the full breakdown: basic info, path details, every query parameter, hash fragment, and SEO/security notes.
- Paste multiple URLs, one per line, to analyze a whole batch in a single pass.
- Copy the full breakdown as JSON using the copy button under each card.
- Not sure what to try? Tap one of the sample buttons (e-commerce URL, UTM tracking URL, hash params, or multiple URLs) to see a working example instantly.
Everything this tool extracts
| Section | Details shown |
|---|---|
| Basic info | Protocol, HTTPS status, hostname, subdomain, registrable domain, domain name (SLD), TLD, port (explicit or default), origin |
| Path | Full path, number of segments, each segment listed, file extension, trailing slash |
| Query parameters | Every key-value pair, decoded, with tracking parameters flagged |
| Hash / fragment | Raw fragment, SPA route path, any parameters after a nested ? inside the hash |
| SEO & security notes | URL length, uppercase letters in path, underscores in path, punycode/IDN domains, embedded username/password |
Common parameter types this URL Parameter Extractor decodes
| Type | Example | Typical use |
|---|---|---|
| Search/filter | ?q=shoes&category=sports | Search terms, category filters, sort order |
| UTM tracking | ?utm_source=newsletter&utm_medium=email | Marketing campaign attribution in Google Analytics |
| Pagination | ?page=2&limit=20 | Which page or how many results to show |
| Session/auth tokens | ?token=abc123&ref=affiliate1 | Referral IDs, one-time tokens, affiliate tracking |
| Ad click IDs | ?gclid=...&fbclid=...&msclkid=... | Google Ads, Meta and Microsoft Ads click tracking |
| Hash/fragment params | #/product?id=42 | Client-side routing in single-page apps |
Who uses a URL analyzer
- Marketers auditing UTM tracking links and ad click IDs before sending a campaign
- Developers debugging query strings, ports and SPA hash routes passed to an API
- SEOs checking for duplicate parameters, long URLs, uppercase paths or underscores that hurt rankings
- Security-conscious users spotting embedded credentials, punycode domains or unusual hosts before clicking a link
- QA testers verifying that redirect and affiliate links carry the right domain, path and parameters
- Anyone who just wants to read a long, messy link without squinting at it
Why use this URL Parameter Extractor
Parsing happens entirely in your browser using the same URL parsing engine built into modern browsers, so results match exactly what the browser itself would send. No link you paste is uploaded or logged anywhere. There is no login, no character limit, and no ads interrupting the analyzer. It loads instantly since it has no external dependencies and works equally well on desktop and mobile.
Common problems when reading URLs
- Percent-encoded values — characters like spaces (
%20or+) and special symbols are automatically decoded into readable text - Duplicate keys — some URLs repeat the same parameter name with different values (e.g.
?tag=sale&tag=new); this tool lists every occurrence rather than only the last one - Missing protocol — if a URL is pasted without
http://orhttps://, the tool assumeshttps://so it can still be parsed correctly - Parameters after a hash — single-page apps sometimes hide real parameters after a
#; this tool checks both the query string and the hash fragment - Multi-part TLDs — domains like
.co.ukor.com.auhave a two-part top-level domain; this tool recognises the common ones so the registrable domain is correct, not just the last segment - IP-address hosts — when the hostname is a raw IPv4 or IPv6 address instead of a domain name, subdomain/TLD breakdown doesn't apply and is skipped
Frequently asked questions
Does this decode percent-encoded (URL-encoded) values?
Yes, every parameter value is automatically decoded, so %20 becomes a space and %26 becomes an ampersand, for example.
Can I extract parameters from multiple URLs at once?
Yes, paste multiple URLs, one per line, and every valid line is parsed in a single pass with its own result card.
Does it work with URLs that don't start with http or https?
Yes, if no protocol is given the tool assumes https:// so domain-only or relative-looking links can still be parsed.
What are "tracking parameters" and why are they flagged?
Tracking parameters like utm_source, gclid or fbclid are added by marketing tools and ad platforms to measure clicks. They're flagged so you can quickly see which parts of a link are actual page data versus attribution tracking.
Why does the domain breakdown skip subdomain and TLD for some URLs?
When the hostname is a raw IP address (IPv4 or IPv6) rather than a domain name, there is no subdomain or top-level domain to extract, so those fields are omitted for that entry.
Is my URL data uploaded anywhere?
No, parsing happens entirely client-side in your browser and nothing is sent to a server.
What is the difference between query parameters and hash parameters?
Query parameters come after a ? and are sent to the server with every request. Hash parameters come after a # and are only readable by JavaScript in the browser — they are never sent to the server, which is why single-page apps often use them for internal state.