URL Parser
Parse and dissect URLs into protocol, host, port, path, and query parameters online. Strip tracking tags (UTM, fbclid), export as JSON, and inspect safely offline.
Input URL / URI
Decomposed URL Anatomy
RFC 3986 & WHATWGExplicit Custom Port in URL
Client Anchor / Route Identifier
Query Parameters Breakdown (5)
| # | Key | Value (Raw) | Value (Decoded) | Type | Actions |
|---|---|---|---|---|---|
| 1 | id | 99 | 99 | Standard | |
| 2 | category | electronics | electronics | Standard | |
| 3 | utm_source | Tracking | |||
| 4 | utm_medium | social | social | Tracking | |
| 5 | fbclid | IwAR123 | IwAR123 | Tracking |
Developer Export & Audit Tools
Anatomy of a Uniform Resource Locator (URL)
Under RFC 3986 and the modern WHATWG URL Living Standard, a Uniform Resource Locator specifies the identity and retrieval location of a network resource. Understanding the precise distinctions between each component is crucial for building robust REST APIs, proxy configurations, and client-side web applications.
Host vs. Hostname vs. Origin
- Hostname: The bare domain label or IP address without any port suffix (e.g.,
api.example.comor[2001:db8::1]). - Host: The complete authority name, combining the hostname with an explicit port if specified (e.g.,
api.example.com:8080). - Origin: The root web security boundary, combining scheme, hostname, and port (e.g.,
https://api.example.com:8080). Web browsers use Origin to enforce CORS and same-origin policies.
Query String Decoding & Tracking Stripping
Query strings convey parameterized key-value arguments using application/x-www-form-urlencoded or percent-encoding. Marketing and analytics platforms frequently append tracking parameters (like utm_source, fbclid, and gclid) that clutter shared links and expose user referral paths. Stripping these tags leaves clean, canonical URLs ready for sharing.
Frequently Asked Questions
Under RFC 3986 and the WHATWG URL standard, Hostname is the domain name or IP address alone (e.g. 'api.example.com' or '[::1]'). Host includes the hostname and the explicit port if one is specified (e.g. 'api.example.com:8080'). Origin represents the root security context composed of the scheme/protocol, hostname, and port (e.g. 'https://api.example.com:8080'). For opaque schemes like mailto: or file:, origin is null.
The Strip Tracking action parses the URL and scans its query string for known analytics, advertising, and marketing telemetry tags, including utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id, fbclid, gclid, msclkid, mc_cid, mc_eid, yclid, _ga, _gl, and prefix tags like pk_* and gbraid. It deletes those tracking keys while preserving all legitimate operational parameters, path segments, and anchor hashes, returning a clean canonical URL.
Our parser leverages the browser's native URLSearchParams and decodeURIComponent engines. It extracts both raw (percent-encoded, e.g. '%20') and decoded (human-readable UTF-8) values for each parameter. When multiple parameters share the exact same key name (e.g. ?tag=react&tag=vue), each occurrence is itemized in the parameter table with its index rather than overwriting previous values.
Yes, completely. The parser fully supports WebSockets (ws:// and wss://), HTTP/HTTPS, FTP, SFTP, and mailto schemes, as well as non-standard custom ports (e.g. :8080, :3000, :5432) and bracketed IPv6 addresses (e.g. http://[2001:db8::1]:8080/path). It also gracefully handles protocol-relative URLs (//example.com) and naked domains by inferring standard secure defaults.
100% private. All URL parsing, string segmentation, query decoding, tracking cleaning, and JSON exports execute exclusively in your local browser's memory using native JavaScript Web APIs. Zero URLs, parameters, authentication credentials, internal intranet hostnames, or API tokens are ever transmitted to any server or third party.