01
Complete component map
Return scheme, host, port, user, path, query, and fragment in one structured result.
Start typing to search 227 tools.
Network
Ready
URL Parser
Split an absolute URL into scheme, host, port, user information, path, query parameters, and fragment.
Absolute URL validation Scheme, host, port, user, path, query, and fragment output Ordered query-pair extraction Repeated parameter grouping
Private browser processing. Your input is processed on this device and is not sent to the Trexmi server.
INPUT Developer source value *
Paste the source value for this specific transformation. Example: Trexmi developer sample
Result
Result ready to review and copy.
About the tool
What URL Parser does
URL Parser splits an absolute address into its structural components: scheme, host, explicit port, user information, path, query string, parsed query parameters, and fragment. The result is formatted as JSON while the original URL remains unchanged.
Parsing helps diagnose API requests, redirects, campaign links, authentication callbacks, and application routes. It can reveal duplicate parameters, encoded nested URLs, unexpected ports, or fragments that never reach the server.
The tool requires a scheme and host and rejects unencoded spaces or control characters. A successful parse explains structure only; it does not request the destination, confirm reachability, or establish that the URL is safe.
How to use
- Paste an absolute URL. Include a valid scheme such as
https://and the hostname. - Run the parser. Input with raw spaces, control characters, or missing authority is rejected.
- Check the authority. Review the scheme, host, optional port, and optional user field.
- Inspect routing data. Compare the path, raw query string, ordered pairs, grouped parameters, and fragment.
- Handle nested values separately. Decode an encoded callback or redirect URL only after identifying it as one parameter.
Built for the task
Why use URL Parser?
Focused controls, predictable output, and a workflow designed around this exact transformation.
02
Query visibility
See the raw query beside ordered occurrences and grouped parameter values.
03
Absolute URL checks
Reject missing schemes, missing hosts, spaces, and control characters before parsing.
04
No reachability claim
The guide distinguishes URL structure from safety, ownership, and network availability.
Useful answers
Questions about URL Parser
Practical details about input, output, privacy, limits, and the best way to use this tool.
01 What does URL Parser return?
It returns the scheme, host, explicit port, user, path, query string, query pairs, grouped parameters, and fragment.
02 Why is a scheme required?
Without a scheme, a value such as example.com/page can be interpreted as a relative path rather than a complete URL.
03 Does an empty port mean an error?
No. Most URLs omit their default port. The parser reports only a port written explicitly in the address.
04 Is the fragment sent to the server?
Normally no. The fragment after # is handled by the browser or client and is not part of the HTTP request target.
05 How are repeated query parameters represented?
Occurrences remain visible in the ordered pair list and are grouped under the same parameter name in the structured result.
06 Does parsing open the URL?
No. This operation only analyzes the supplied text.
07 Can a parsed URL still be dangerous?
Yes. Valid structure does not establish ownership, reputation, safety, or intended destination.
08 Should I paste signed or reset links?
No. Query parameters may contain active credentials, tokens, or personal data and should be treated as secrets.
Learn URL Encoding
Read the complete URL Encoding Guide
Learn percent-encoding, UTF-8 URLs, query strings, path segments, spaces, plus signs, and double-encoding mistakes.
- Percent-encoding rules
- Query strings and paths
- UTF-8 and double encoding
Read guide
Practical explanations and examples
URL components explained
The scheme appears before the first colon and commonly identifies HTTP or HTTPS. The authority contains the host and may include user information or an explicit port. The path identifies a location within that authority, while the query and fragment add optional state.
Default ports are usually omitted. A missing port therefore does not mean the address is incomplete. User information inside a URL is supported by syntax but should be handled carefully because credentials can leak through logs and browser history.
Raw queries, ordered pairs, and grouped parameters
The query begins after ? and ends before #. A raw query preserves its transmitted representation. Ordered pairs show every name-value occurrence, including duplicates. Grouped parameters make repeated values easier to inspect.
Frameworks do not interpret repeated keys and bracket notation identically. Use the parsed result to understand the input, then verify application-specific nesting and precedence rules in the receiving system.
Percent encoding and nested URLs
Reserved characters can change URL structure, so values often use percent encoding. A redirect parameter may contain an entire encoded URL. Parse the outer URL first, identify the specific parameter, and then decode that value separately.
Repeated decoding is risky because a once-decoded percent sequence may become active syntax. Preserve the original string and decode only the layer required by the protocol.
Common URL debugging workflows
For API failures, compare the scheme, host, port, route path, and parameter names with the API documentation. For campaign links, verify UTM names, duplicates, blank values, and encoded landing-page state. For authentication callbacks, inspect redirect targets without exposing authorization codes or tokens.
A parsed URL can still point to a nonexistent or inaccessible resource. Reachability and HTTP status require a separate network check.
URL security and privacy
Look-alike domains, unexpected ports, misleading user-information sections, and nested redirects deserve separate review. Parsing does not detect phishing or malware. Avoid sharing URLs containing session identifiers, signed download parameters, password-reset tokens, or private customer information.
Related Trexmi tools
Use Query String Parser for parameter-focused output, URL Encoder for one component, URL Decoder for encoded text, or HTTP Header Checker for a public response.
After verifying an API endpoint, translate a copied command with cURL to Fetch or cURL to Python Requests.
Authoritative reference
Review RFC 3986 and the WHATWG URL Standard for the syntax and browser parsing models relevant to your application.