URL Parser
Break a URL down into protocol, host, port, path, query parameters, and hash.
Every calculation runs locally in your browser. Nothing you enter here is sent to a server.
Query parameters
For informational and educational purposes only — not professional or technical advice, and not a substitute for consulting a qualified professional about your specific situation. TrueMeasureKit is not liable for decisions made based on these results. See our Terms of Service.
Why this doesn't use a regex
URLs have more edge cases than they look like — IPv6 host literals, internationalized domain names encoded as punycode, percent-encoded characters in the path, and query strings with repeated keys. Rather than reimplement the URL spec with a regular expression, this uses the browser's built-in URL constructor, which handles all of that correctly by construction — the same parser the browser itself uses for navigation.
Frequently asked questions
What's the difference between a URL's path and its query string?
The path identifies a specific resource location (everything after the domain, before a ?). The query string (after the ?) passes key-value parameters to that resource — the same path can return different results depending on query parameters.