How to parse a URL
- Paste a full link into the box above.
- Press Try an example if you want to see a sample first.
- Read each part in the results panel.
- Scan the parameter list for the values you care about.
- Copy any part you need.
What this URL parser gives you
- Each main part of the link on its own line.
- Every query parameter listed with its value decoded.
- The origin that browsers compare for security rules.
- The domain and subdomain split apart.
- Path segments listed one by one for routing work.
- A warning when a link hides a username and password.
A URL has more parts than people remember
Most links look simple until one does not. Think of a tracking link with fifteen parameters. Think of a redirect chain with a link nested inside a link. Think of an API endpoint with a port and a fragment. Your eyes alone will read those slowly and make mistakes.
A URL parser makes the structure obvious. You see which host the link really contacts. You see the path. You see exactly which parameters it sends and with which values.
Parsed the way browsers parse
This tool uses the URL engine built into your browser. That engine follows the WHATWG standard. It is the same code that runs when you type an address into the bar.
That matters. URL parsing has more edge cases than most people expect. A homemade regular expression will disagree with the browser on some of them. This tool converts international domain names to their punycode form. It knows default ports. It resolves dot segments in paths. It does each step exactly as a browser would.
How to read each part
| Part | Example | What to know |
|---|---|---|
| Protocol | https: | How the browser connects |
| Host | shop.example.com | The server the link really contacts |
| Port | 8080 | Blank when the default applies |
| Path | /shoes/red | The page or resource on that server |
| Query | ?size=9 | Extra data for the server |
| Fragment | #reviews | Stays in the browser and never reaches the server |
The origin joins the protocol, host and port. Browsers compare origins for the same origin policy. That explains why an API on a different port needs CORS headers.
Credentials are a username and password placed before the host. Browsers dropped support for them long ago. They now serve as a strong phishing signal. So the tool masks the password.
Query parameters hold the real information
The tool lists each parameter with its value decoded. You skip copying values into a decoder one at a time.
Repeated keys appear as separate entries. A link like ?tag=a&tag=b is a valid way to pass a list. A parser that kept only the last value would mislead you. The tool also marks empty values clearly. To most servers ?debug= means something different from no debug parameter at all.
Use a URL parser on suspicious links
Parse any link you did not expect. The host is the part that matters. A phishing link often puts a familiar brand in the path or a subdomain. The real host is something else entirely.
Read example.com.attacker.net as a host name and the trick becomes obvious. A quick scan of a long link rarely shows that. This tool only reads the text. It never visits the link. So it is safe to paste anything here.
Common URL parser questions
Do I need to type https://?
No. The tool assumes https when no scheme appears. A status line tells you when it does that.
Why is my port blank?
The link uses the default port for its protocol. That is 443 for https and 80 for http.
Tips for reading links safely
- Read the host from right to left. The last two parts name the real site.
- Treat any link with a username and password as suspicious.
- Check redirect parameters for a second hidden link.
- Remove tracking tags before you share a link.
- Paste a link here before you click it in an odd email.
Who uses a URL parser?
Developers debug routes and API calls. Marketers check campaign tags. SEO teams audit redirects. Security teams inspect phishing reports.
Your links stay private
The tool works in your browser and uploads nothing. Need to decode a single value? Use the URL decoder. Want to build a link from scratch? The URL encoder helps. Found Base64 in a parameter? Try the Base64 decoder.