URL Parser
Split a URL into scheme, host, port, path, query and fragment, then drop parameters and rebuild
待解析的 URL
缺少协议时会自动按 https:// 补全后再解析，因此 www.uutools.com/tools 这类写法也能正常拆解。
About this tool
A URL looks complicated but always follows the same small set of parts. This tool shows each part separately, which helps when debugging APIs, cleaning shared links and tracing parameter issues:
- Full breakdown: scheme, hostname, port, host with port, domain suffix, origin, path, query string, fragment, credentials and the complete address, 12 parts in all
- Parameter table: splits on
&and decodes each value, with one-click copy per row - Path segments: expands every level after
/with the cumulative path, useful for RESTful routes - Remove and rebuild: untick a parameter to drop it and get a new URL instantly, no manual string editing
- Scheme fill-in: shorthand such as
www.uutools.com/toolsis parsed as https automatically - Many forms: private IPs with ports,
user:passcredentials,file://paths anddata:resources all parse
When to use it
- Confirming the real host, port and path prefix of an API request
- Stripping tracking parameters such as
utm_sourceandfromfrom shared links - Finding which parameter changes the result when testing filters or A/B variants
- Copying an exact origin for reverse proxy or CORS allowlists
- Validating path levels and encoding when scripts build URLs
URL structure reference
| Part | Example | Notes |
|---|---|---|
| scheme | https: | If omitted, the browser assumes https or follows the current page scheme |
| credentials | user:pass@ | Plain text in the address, largely blocked by mainstream browsers now |
| host | api.example.com:8080 | Domain or IP, optional port, maps to the Host header |
| path | /v3/orders/10086 | Slash-separated levels, the main input to server routing |
| query | ?fields=id&status=1 | Key-value pairs encoded with percent-encoding |
| fragment | #top | Never sent to the server, used by in-page anchors or client routing |
Common questions
- How do I decode Chinese or symbols in a parameter? The table already shows decoded values, so
%E4%BD%A0%E5%A5%BDappears as the original text; use the URL encoder to go the other way - Why is the port blank? No port means the default for the scheme, 443 for https and 80 for http, which the tool shows in parentheses
- Does the server see anything after the hash? No. Everything after
#stays in the browser and never appears in server logs
To identify a visitor browser and system, use the User-Agent parser; to resolve a domain to an IP and region, use IP lookup. All parsing runs in the browser and the URL is never uploaded.