In this article
A URL taken apart
Take https://shop.example.com:8443/products/shoes?colour=red&utm_source=newsletter#reviews:
| Part | Value | Meaning |
|---|---|---|
| Protocol | https: | Secure connection (http is unencrypted) |
| Subdomain | shop | A section run under the main domain |
| Domain | example.com | Who owns the site – the key part for trust |
| Port | 8443 | Usually hidden; 443 for https, 80 for http |
| Path | /products/shoes | Which page |
| Query string | colour=red&utm_source=newsletter | Extra parameters for the page or tracking |
| Fragment | #reviews | A position on the page; never sent to the server |
Parse any address
- Paste a URL into the URL Parser.
- See protocol, host, port, origin, path and fragment separately.
- Read every query parameter in a table, decoded into normal text.
- Spot tracking codes – utm_*, gclid, fbclid and similar – which are flagged automatically.
The tool uses the browser’s standard URL parser, the same one that decides where your browser actually goes.
Reading the domain correctly: a safety skill
The real domain is the part just before the first single “/” after “https://”, read from right to left. In https://paypal.com.secure-login.net/account, the domain is secure-login.net – not PayPal. Scammers put familiar names in subdomains or paths to fool people. Also watch for look-alike characters, such as “rn” pretending to be “m”, or a zero instead of “o”.
Query parameters in practice
- Filters and searches:
?q=laptop&sort=price. - Campaign tracking:
utm_source,utm_medium,utm_campaign– build them with the UTM Builder. - Ad click IDs:
gclid(Google Ads),fbclid(Facebook) – safe to remove when sharing a link.
Subdomains vs folders
A blog can live at blog.example.com (a subdomain) or example.com/blog/ (a folder). Both work for search engines, but a folder is usually simpler to manage and keeps everything under one site in analytics and Search Console. Subdomains suit separate applications, such as a help centre or a shop run on another platform.
Ports and local addresses
Developers often see addresses like http://localhost:3000 or 192.168.1.1. These point to your own computer or local network, not the public internet. If a link you receive points to such an address, it will not work for you – it was copied from someone’s test setup.
Why the fragment matters
Everything after “#” stays in the browser. It is used to jump to a heading, and by some web apps for navigation. Because servers never see it, analytics tools cannot track fragments unless a script reports them.
Uses for site owners
- Check campaign links before an email goes out.
- Debug redirects that drop or duplicate parameters.
- Find duplicate-content issues caused by parameters, and fix them with canonical tags.
Encoded parts
Parameters often contain % codes. The parser decodes them for you; to encode or decode text yourself, use the URL Encoder and URL Decoder. For readable page addresses, see the Slug Generator.