URL Parser

Break any web address into its building blocks — scheme, host, port, path, query string and fragment — and see every query parameter listed separately with its decoded value.

How to use it

1. Paste the full address.
2. Run the parser.
3. Read each component in the results table.

The parts of an address

Take https://shop.example.com:8080/products/shoes?color=red&size=42#reviews:

• Scheme – https
• Host – shop.example.com
• Port – 8080 (usually omitted)
• Path – /products/shoes
• Query – color=red&size=42, split into two parameters
• Fragment – reviews, a jump point inside the page

When it helps

• Checking UTM tags on marketing campaigns
• Debugging API requests and callback addresses
• Spotting tracking parameters before you share something
• Understanding redirects and affiliate addresses

Parsing vs decoding

The parser shows structure. If the address is full of codes such as %20, run it through our URL Decoder first to make it readable.

Limitations

The tool reads the text you provide; it does not visit the address or confirm that the page exists or is safe.

A worked example

A marketer wonders why a campaign shows up as "direct" traffic in analytics. Parsing the advert's address reveals utm_source written as utm-source with a hyphen, so analytics ignored it. Fixing the parameter name restores correct attribution.

Understanding UTM parameters

• utm_source – where the visitor came from, such as newsletter or facebook.
• utm_medium – the channel, such as email, cpc or social.
• utm_campaign – the campaign name, such as spring_sale.
• utm_term and utm_content – optional details for keywords and ad variations.

Spotting tracking you may not want to share

Addresses copied from emails and social apps often carry identifiers like fbclid, gclid or mc_eid. Parsing shows them clearly so you can remove them before sharing a cleaner address with others.

Developer uses

1. Checking OAuth callback addresses and their parameters.
2. Confirming that values are encoded correctly before sending an API request.
3. Debugging routing issues caused by unexpected trailing slashes or fragments.

Related tools

• URL Decoder – make encoded values readable
• URL Encoder – encode a value safely
• Redirect Checker – see where an address leads

Glossary of address terms

• Subdomain – the part before the main name, such as shop in shop.example.com.
• TLD – the ending, such as .com or .org.
• Trailing slash – a final /, which some servers treat as a different address.
• Anchor or fragment – the part after #, handled only by the browser and never sent to the server.

Why fragments matter

Because the part after # never reaches the server, analytics and server logs do not see it. Single-page apps sometimes use it for navigation, which can confuse tracking — parsing the address makes this easy to spot.