The parts of a URL
Every web address is made of several parts, and each one has a job. Knowing them helps when you build links, set up redirects, debug an API call or check which tracking parameters a marketing link contains. This parser uses the browser's own URL engine, so it splits addresses exactly the way a browser does.
https://shop.example.com:8080/products/shoes?color=black&size=9#reviews
└scheme┘ └──── host ────┘└port┘└──── path ────┘└─── query ───┘└ hash ┘
How to use the parser
- Paste a full URL into the box. If you leave out
https://, it is added for you. - Read each part in the table: protocol, origin, host, port, path, query and fragment.
- Check the query parameters table, where every value is decoded so
%20appears as a space.
What each part means
- Protocol (scheme): how to connect, usually
https:. - Hostname: the domain name of the server. Anything before the main domain, such as
shop, is a subdomain. - Port: a network door number. It is hidden when it is the default (443 for https, 80 for http).
- Path: the location of the page on the server.
- Query string: extra information after
?asname=valuepairs joined by&. Search terms, filters and UTM tracking codes live here. - Fragment: the part after
#. It points to a section of the page and is never sent to the server. - Origin: scheme, host and port together. Browsers use it for security rules such as CORS.
Frequently asked questions
What are utm_ parameters?
UTM parameters such as utm_source and utm_campaign tell analytics tools where a visitor came from. They do not change the page content.
Can a parameter appear twice?
Yes, for example ?tag=a&tag=b. Both rows are listed in the table.
How do I encode a value before adding it to a URL?
Use the URL Encoder in component mode.