Does the parser visit the URL?

No. It uses the browser URL parser without making DNS, HTTP, or preview requests.

How are URL passwords handled?

Password values are masked by default and can only be revealed with an explicit local action.

URL Parser – Inspect URL Structure & Query Parameters

What makes up a URL?

A URL can contain a scheme, credentials, hostname, port, path, query string, and fragment. The anatomy strip separates present components by both labels and boundaries, so the structure does not rely on color alone.

Scheme, hostname, and path

The scheme describes how a resource would be addressed, such as HTTPS. The hostname identifies a server name or IP address. The pathname locates a resource within that origin. Parsing these fields does not contact the server.

Query parameters explained

The text after ? contains key-value pairs. Keys may repeat, as in ?tag=php&tag=vue, so this parser preserves each entry rather than collapsing them into an object. Sorting, removing, decoding, and adding parameters only changes the local rebuilt preview.

Fragments, ports, and credentials

A fragment begins with # and usually identifies a location handled by the client. An explicit port overrides the scheme’s default. URLs can include usernames and passwords, but embedding secrets in URLs is risky; passwords are masked here by default.

Frequently asked questions

Does parsing make a network request?

No. The browser’s local URL and URLSearchParams APIs parse and rebuild the string without DNS or HTTP activity.

Can I safely open the rebuilt URL?

Review it first. This tool intentionally provides copy only and never opens or previews an address automatically.