Break down a URL in the browser
Enter a long URL to inspect its components, Path Segments, and encoded and decoded Query Parameter values without accessing the URL.
Parse a URLConclusion: Display the query as ordered pairs and compare encoded and decoded values
For https://example.com/search?q=%E6%9D%B1%E4%BA%AC&page=2, verify q=Tokyo and page=2. Do not simply convert to an object; preserve every row even when multiple keys have the same name.
Decoded output alone does not show the original %XX or +, while encoded output alone makes the actual characters difficult to read. Check both on the same line.
Keep the input URL, compare the normalized URL and each Component, and check Query and Fragment separately.
List Query Parameters without breaking them.
Queries separate Parameters with & and treat the first = as the boundary between Key and Value. However, & and = within a Value must be Percent-Encoded.
The current tool displays encoded keys and values and decoded keys and values in input order. It does not perform dedicated sorting or deletion and retains the original order.
| Account to check | What to check | judgment |
|---|---|---|
| Raw Query | From after ? to before # | Preserve the original expression |
| Key / Value | First = | Check by line |
| Decode | %XX and + | Compare display differences |
| Duplication | All rows with the same Key name | Do not overwrite |
Procedure for checking with the URL analysis tool
- Enter the completed URL.
- Check the Raw Query in the “Query” component.
- Compare Encoded Key/Value and Decoded Key/Value line by line.
- Copy the key and value from required rows, or query JSON.
Query JSON is also an array format, so it can preserve same-name Key order and multiple Values.
How to isolate results that differ from expectations
If the expected parameter is not visible, check the order of ?, &, =, and #, and the value's encoding.
If & in a Value is not Encoded, it is split into a separate Parameter. A string placed after # is a Fragment and does not appear in the Query list.
- Whether ? is at the query start position
- Whether & remains in the value
- Whether there is a parameter before #
- Check that you are not looking at only one key with the same name.
Supported scope of the current URL analysis tool
DevelopTools does not access input URLs; it parses strings only with the browser's standard URL class. It supports absolute URLs and relative URLs with a specified base URL, and separately displays the input URL, normalized URL, protocol, origin, username, host, hostname, port, pathname, search, hash, and HTTPS determination. Path separators and query parameters retain input order, and encoded and decoded values can be checked side by side.
| Account to check | Current tool operation |
|---|---|
| URL component | Display the input URL and normalized URL, protocol, origin, host, hostname, port, path, query, and fragment. |
| Relative URL | When a base URL is provided, resolve to an absolute URL using the URL class |
| Path | Display Slash-delimited Segments in both Encoded and Decoded forms. |
| Query | Display encoded keys and values and decoded keys and values without losing order, duplicate keys, or empty values |
| Safety Notes | Supplementary display for HTTP, credentials, active scheme, non-standard ports, Punycode, long URLs, and keys that appear sensitive |
| output | Copy the normalized URL, query JSON, parsed JSON, and individual values to the clipboard |
UTM-specific classification, recursive analysis of Nested URLs, Parameter removal, URL reachability checks, HTTP Status, Redirect tracking, and Downloads are not performed. Check UTM and redirect_uri as ordinary Parameter rows; if necessary, Copy the value and enter it step by step into URL Encoder / Decoder or the URL analysis tool.
Do not confuse URL analysis with safety assessment
Even if a URL can be broken down into Scheme, Host, Path, and Query, this cannot determine whether the Website is safe, whether it is Phishing or Malware, or whether the destination exists. The current Tool disables connect-src and does not make HTTP Requests, perform DNS checks, or follow Redirects to entered URLs.
URLs may contain Access Tokens, OAuth Codes, JWTs, Email addresses, User IDs, Internal Hosts, and search terms. Because URLs can remain in Browser History, Access Logs, Referers, Analytics, and screen shares, do not paste real data into article Samples; remove values or replace them with Dummy values before sharing. Input URLs are not stored; only Theme settings are stored in LocalStorage.
URL analysis is not communication or a safety check. It also does not justify putting Secrets in URLs, so visually inspect the Original URL and copied content before publishing.
Check URL specifications and Web APIs in primary sources
Check browser URL parsing, normalization, and serialization against the WHATWG URL Standard; general URI syntax against RFC 3986; and JavaScript URL and URLSearchParams against MDN. Prioritize official Google Analytics documentation for UTM parameters, and validate individual framework behavior using its official documentation and actual received values.
Example: List the three parameters in a search URL
Parse https://example.com/search?q=%E6%9D%B1%E4%BA%AC&page=2&sort=date.
The three lines q, page, and sort are displayed in input order, allowing comparison of q's Encoded Value and Decoded Value, “Tokyo.”
- Parse a URL
- Confirm that there are three Queries.
- Compare q's Encoded and Decoded values.
- Copy page and sort.
Use dummy values to verify operations, rather than URLs containing production tokens or personal information.
Frequently asked questions
- When you analyze the URL, do you access the link?
- No. It only parses the input string with the browser's standard URL class; it does not Fetch the target URL, check DNS, or follow Redirects.
- Can a URL parsing tool also check website safety?
- No. It displays cautions such as Schemes or Keys that appear sensitive, but it does not determine Phishing, Malware, certificates, or the legitimacy of a connection destination.