URL parser

See every part of a URL

A URL is made of several parts. In https://mybotsy.com/blog/dns-guide?utm_source=newsletter&ref=42, the scheme is https, the host is mybotsy.com, the path is /blog/dns-guide and the query is utm_source=newsletter&ref=42. URLs can also include a port, a username and a fragment (the part after #).

Paste any URL and the parser splits it into those parts so you can read long tracking links, check API endpoints, and spot suspicious domains hidden at the start or end of a long link.

It's a simple way to understand exactly what a link contains before you use it, share it or debug it.

How to use the url parser

1. Paste the full URL.
2. Submit to parse it.
3. Read the scheme, host, path and query.
4. Copy the part you need.

Examples

A shop link

Input:

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

Output:

scheme: https
host: shop.example.com
port: 8080
path: /products/shoes
query: color=blue&size=42
fragment: reviews

The query is also listed as separate parameters: color = blue, size = 42.

Login details in a link

Input: https://user:[email protected]/a/b.html

Output:

scheme: https
host: example.com
user: user
pass: pass
path: /a/b.html

Everything before @ is a username and password, not the website. Phishing links use this trick: https://[email protected] goes to evil.example.

A tracking link

Input: https://mybotsy.com/blog?utm_source=newsletter&utm_medium=email

Output:

query parameters:
utm_source = newsletter
utm_medium = email

Each parameter is shown on its own, which makes long tracking links easy to check.

Common uses

• Inspecting UTM and tracking parameters in marketing links.
• Debugging API endpoints and query strings.
• Checking the real domain of a long or suspicious link.
• Extracting the path for redirects or analytics filters.
• Teaching how URLs are structured.
• Checking which parameters an affiliate or shared link adds before you post it.

Tips and things to know

• The host is what matters for safety: in https://paypal.com.secure-login.example/ the real domain is secure-login.example.
• Encoded query values are easier to read after the URL decoder.
• Build tagged links with the UTM link generator, and follow redirects with the URL redirect checker.

Edge cases and limitations

• Include the scheme. mybotsy.com/blog without https:// returns no parts.
• In the parameter list, a value containing = is cut at the second = (q=a=b shows q = a), and a parameter with no value (&flag) shows as empty. Read the full query line for the exact text.
• Encoded values (%20, %2F) are shown encoded. Decode them with the URL decoder.

Frequently asked questions

What are the parts of a URL?

Scheme (https), host (domain), optional port, path (/page), query (?key=value) and fragment (#section).

What is a query string?

The part after ? that holds key=value parameters separated by &.

Is the fragment sent to the server?

No. The #fragment is handled by the browser and isn't sent in the HTTP request.

How can I spot a fake link?

Look at the host, especially the part right before the top-level domain like .com. That's the real website.

Why does the parser show nothing?

The URL is probably missing https:// at the start, or contains spaces. Add the scheme and remove any spaces.

Does it check whether the link is safe?

No. It only shows the parts of the address. Look at the host to see where a link really goes.

Related tools

• URL decoder: Decode URL input to back to a normal string.
• URL encoder: Encode any string input to URL format.
• UTM link generator: Easily add UTM valid parameters and generate a UTM trackable link.
• URL redirect checker: Check for 301 & 302 redirects of a specific URL. It will check for up to 10 redirects.