Online Tool Store
URL ވިވިކުރި
URL ތިޔަ ، ވަިސ ، ނަވާރި ، ސްވާ ، ވަތް ، ކުތަ ، ނިޔާ ، ނަދި ހާސް ، ވިވިކުރި
🔒 މި ޓޫލް ހިނގަނީ ހަމައެކަނި ތިޔަބޭފުޅާގެ ބްރައުޒަރގައި. ތިޔަބޭފުޅާގެ ފައިލްތައް ސަރވަރަކަށް ފޮނުވޭކަށް ނުވެ.
Example shown — replace it with your own URL.
How it works
- Paste a full URL, including its protocol (e.g. https://).
- It's broken down into protocol, credentials, host, port, path, query parameters, and hash as you type — percent-encoded path or fragment segments also show a decoded version, and recognized campaign-tracking parameters (utm_source, utm_medium, and the rest) are flagged with a UTM badge.
- Copy any single field, the full URL, the whole breakdown as JSON, or a query parameter's value — the address bar also updates to a shareable link back to this exact result.
FAQ
Does the URL or its contents get sent anywhere?
No. Parsing happens with your browser's built-in URL API, entirely on your device — nothing you paste here is uploaded or logged.
Can it parse a relative path like /path?query=1?
No — it needs a full, absolute URL including the protocol (e.g. https://example.com/path?query=1). A relative path on its own has no host to resolve against, so it's rejected with an error rather than guessed at.
What does 'Decoded path' or 'Decoded fragment' mean?
URLs can only contain a limited set of characters, so anything else (spaces, non-ASCII text, etc.) gets percent-encoded, e.g. "%20" for a space. Those rows show the human-readable version after decoding — they only appear when the raw value actually contains encoded characters.
Are the username and password fields safe to use?
They're parsed the same way every other field is — locally, in your browser. That said, credentials embedded directly in a URL (https://user:pass@host/) are inherently visible to anything that can read the URL (browser history, server logs, this page), so treat any URL containing them as sensitive.
Why does it show "(default)" for the port?
When a URL doesn't specify a port explicitly, the browser's URL parser leaves it blank because the scheme's default applies (443 for https, 80 for http). "(default)" makes that explicit instead of showing a confusing empty value.
What does the 'UTM' badge on a query parameter mean?
It flags one of the documented Google Analytics campaign-tracking parameters — utm_source, utm_medium, utm_campaign, utm_term, utm_content, utm_id, or utm_source_platform. These show up constantly in marketing links, so they're called out to make a long query string easier to scan.
How does the shareable link work?
As you type, this page's own address bar updates to include the URL you're parsing. Copy that address and send it to someone else — opening it loads this tool with the same URL already parsed, so you don't have to re-paste it into a message.
How we compare
| Feature | Online Tool Store | CodeShack | ParseUrlOnline |
|---|---|---|---|
| No file upload — runs in your browser | ✓ | ✓ | Not stated |
| Decodes percent-encoded path/fragment automatically | ✓ | Not stated | Not stated |
| Copy button on every field, not just the whole URL | ✓ | ✓ | Not stated |
| Copy full breakdown as JSON | ✓ | Not stated | Not stated |
| Flags recognized UTM campaign parameters | ✓ | Not stated | Not stated |
| Shareable link back to a specific parsed URL | ✓ | Not stated | Yes (via URL fragment) |
The browser's own devtools console can do everything this tool does — new URL(...) is the same API running underneath both — but it means opening devtools and typing code. CodeShack matches this tool's per-field copy buttons, and ParseUrlOnline's shareable-link trick is worth borrowing — both are folded in here, on top of automatic UTM tagging and a live breakdown that updates as you type instead of waiting for a "Parse" click.