Web Tools
URL Parser & Inspector
Inspect URL components and query parameters.
URL Parser & Inspector tool
Loading tool…
Jump to a section
About This Tool
URLs often carry several pieces of information in one string: the scheme used to access a resource, the host, an optional port, a path, query parameters, and a fragment. This inspector separates those parts so you can debug links, APIs, redirects, tracking parameters, and web application routes without manually splitting punctuation or accidentally losing repeated parameters.
How To Use It
- Paste an absolute HTTP or HTTPS URL, including the scheme such as https://.
- Review the normalized URL and each structural component.
- Inspect query parameters individually; repeated parameter names remain separate and in their original order.
- Copy any component you need for debugging or documentation.
Examples
Inspect an API URL
For https://api.example.com:8443/v1/items?page=2#results, the hostname is api.example.com, port is 8443, path is /v1/items, query is ?page=2, and fragment is #results.
Repeated query parameters
A URL ending in ?tag=web&tag=tools contains two tag entries. The inspector preserves both instead of converting them into an object that would lose one value.
Percent-encoded values
In ?q=hello%20world, the raw query remains visible while the parameter value is shown as hello world using the browser's standard URLSearchParams decoding behavior.
Plus signs in query values
In ?q=hello+world, URLSearchParams displays the value as hello world because plus signs are treated as spaces in form-style query parsing.
Useful Notes
Anatomy of an HTTP URL
A typical URL combines a scheme such as https:, a hostname, an optional non-default port, a pathname, an optional query beginning with ?, and an optional fragment beginning with #. The origin is the scheme, hostname, and effective non-default port together.
Browser-standard parsing
This tool uses the browser's built-in URL and URLSearchParams implementations rather than a custom parser. Browsers may normalize valid input by trimming surrounding whitespace, removing a default HTTPS port, resolving dot segments in paths, or serializing percent encoding consistently. The normalized URL therefore may not be character-for-character identical to the pasted text.
Query strings and duplicate keys
Query parameter names are not required to be unique. Some APIs intentionally use forms such as tag=a&tag=b. The inspector displays entries as an ordered list so duplicate keys and empty values are not silently overwritten.
Decoded parameter display
The query table shows parameter names and values after URLSearchParams decoding. Percent-encoded bytes such as %20 become readable characters, and unescaped + signs in query values are displayed as spaces.
Privacy and scope
Parsing happens locally and this tool does not request the URL or test whether its host exists. It supports HTTP and HTTPS URLs only. URLs with embedded usernames or passwords are rejected so credentials are not echoed into the results interface.
Not a security verdict
A successfully parsed URL can still be unsafe, misleading, expired, or controlled by someone else. Use this page to inspect structure, not to decide whether a link should be trusted.
FAQ
Does this tool visit the URL I paste?
No. It parses the text locally with browser URL APIs; it does not fetch the page, perform DNS lookup, or verify that the destination exists.
Why did :443 disappear from my HTTPS URL?
443 is the default port for HTTPS. Browser URL normalization can omit an explicitly written default port because it does not change the effective destination.
What is the difference between a query and a fragment?
The query begins with ? and commonly supplies parameters to the server or application. The fragment begins with # and identifies a location or client-side state; browsers normally do not send the fragment in an HTTP request.
Is URL parsing the same as URL encoding?
No. Parsing separates a complete URL into components. Encoding converts characters into a form suitable for URL components. Use Hanakash's URL Encode & Decode tool when you need percent encoding or decoding.
Why did a plus sign become a space?
URLSearchParams follows form-style query parsing, where an unescaped + in a query value represents a space. Use %2B when a literal plus sign is required.
Can this tell me whether a URL is safe?
No. It only parses structure locally. It does not check reputation, scan content, verify ownership, or follow redirects.