Guide
Anatomy of a URL
The parts of a URL
https://user:pass@shop.example.com:8443/products/shoes?color=blue#reviews \___/ \_______/ \______________/ \__/\_____________/ \________/ \_____/ scheme userinfo hostname port path query fragment
- Scheme: how to fetch the resource, usually
https. - Hostname and port: which server to contact. The port is omitted when it is the scheme's default (443 for HTTPS, 80 for HTTP).
- Path: which resource on that server.
- Query: key-value parameters after
?, separated by&. - Fragment: the part after
#. It is handled by the browser and never sent to the server.
Cleaning tracking parameters
Links shared from newsletters and social media often carry tracking parameters such as utm_source, utm_medium, utm_campaign, fbclid and gclid. Remove them in the parameter editor to get a shorter, cleaner link before sharing it. When building your own campaign links, add UTM parameters here and the tool encodes them correctly.
Security tip
Phishing links often hide the real destination: in https://paypal.com@evil.example/ the part before @ is just a username, and the actual host is evil.example. The Hostname row shows you where a link really goes.
Frequently asked questions
Do I need to include https://?
No. If you paste a bare domain such as example.com/page, the parser assumes https.
Are parameters encoded automatically?
Yes. Type values normally; spaces, ampersands and other special characters are percent-encoded in the rebuilt URL.
Can a parameter appear more than once?
Yes, for example ?tag=a&tag=b. Each occurrence is listed separately and kept in order.