Zellio.io

URL Parser & Query Inspector

Break any URL into its parts and inspect every query parameter.

Runs locallyWorks offlineShare link carries settings, never your data
Send output toSubnet CalculatorMAC Address AnalyzerSlug / URL EncoderBuild a workflow from thisOutput stays on this page until you send it.

Frequently asked questions

Are the URLs I paste uploaded?

No. Everything runs locally in your browser using standard web APIs — your text, files and inputs are never uploaded to a server, so the tool works even offline once the page has loaded.

Does it decode percent-encoded parameters?

Yes. Each query parameter value is shown URL-decoded (for example %20 becomes a space), while the key is listed exactly as it appears. This automatic decoding makes it easy to read what data is actually being passed in the URL without manually translating percent-encoded characters. For example, a parameter like search=hello%20world%21 is displayed as search: 'hello world!' so you can immediately understand the value. This is especially useful for debugging URLs with non-ASCII characters, special symbols, or spaces that are encoded for transmission.

What happens if I leave off http:// or https://?

The parser assumes https:// so you can paste a bare host like example.com/path?x=1 and still get a full breakdown. This convenience feature lets you paste URLs quickly without worrying about the scheme, and the parser intelligently adds https:// as the modern standard. If you need to parse an http:// or custom-scheme URL, you can include the scheme explicitly and the parser will respect your input. This flexibility makes the tool work well for quick URL analysis without requiring a complete URL format.

Pro tips

  • Paste any URL to instantly extract protocol, domain, path, query parameters, and fragments without regex parsing.
  • Decode URL-encoded special characters automatically to read parameter values with spaces and symbols correctly.
  • Inspect individual query parameters without manually parsing the URL string or using browser dev tools.
  • Validate URLs are properly formatted before using them in API calls, redirects, or email links.

About URL Parser & Query Inspector

Parsing runs through the browser's own URL implementation, so the breakdown matches what a browser will genuinely do with the link rather than approximating it. Parameters are shown decoded, which is how a value that was double-encoded upstream gives itself away.

A URL packs a lot of structure into one string. This parser breaks any URL into its parts — protocol, username and password, hostname, port, path, fragment and origin — and lists every query-string parameter in a decoded table so you can see exactly what a link carries. Paste a URL with or without a scheme; if you omit it, https:// is assumed.

It is built for the URLs that go wrong: a redirect chain that quietly drops a parameter, an analytics tag with a duplicated key, an OAuth callback whose state value arrived double-encoded. Listing every parameter separately is usually enough to show which one is malformed.

Reading a hostname correctly is a security skill, not just a debugging one. Hostnames resolve right to left: in shop.example.co.uk the top-level domain is uk, the registered domain is example.co.uk, and shop is a subdomain. Phishing exploits exactly this — example.com.attacker.net is a page on attacker.net, with the familiar name placed first because that is what a hurried reader anchors on. Seeing the host isolated from the rest of the URL makes the real registrable domain obvious.

The fragment behaves unlike every other component and it explains a recurring class of confusion. Everything after the hash is handled entirely by the browser and is never transmitted to the server, so it appears in no access log, no referrer header and no server-side analytics. When a value is visible in the address bar but absent from the backend, being in the fragment rather than the query string is almost always why.

Tracking parameters are worth recognising on sight. Anything beginning utm_ is campaign attribution added by the sender rather than required by the destination, and fbclid, gclid and similar are click identifiers appended by a platform. All of them can normally be stripped without changing which page you land on, which makes a shared link shorter, cleaner and less revealing about where the recipient found it.

Common use cases

  • Web developers debugging redirect chains and API request URLs by inspecting each component for correct parameter values.
  • Marketing teams analyzing campaign tracking URLs to decode UTM parameters and verify data is being captured correctly.
  • Security analysts identifying malicious URLs by decomposing them to spot suspicious subdomains, paths, or encoded parameters.
  • QA testers validating API response links and pagination URLs contain correct query strings before shipping features.
How it comparesUnlike browser dev tools requiring network inspection or regex parsing libraries, our parser instantly displays all URL components visually, offering faster analysis than parsing.org and more readable output than command-line tools like curl --verbose for quick URL validation.