Free tool · runs in your browser

URL Inspector

Inspect a URL’s origin, host, port, path, parameters and fragment, then spot credentials, secrets, duplicates and ambiguous normalisation.
Local processing No data sent No account Web and API

Powered by WHATWG URL

URL to inspect

Absolute URL only. No domain is resolved and no request is sent.

Examples

How does a browser interpret a URL?

A URL describes a resource through a scheme, authority, path, query string and optional fragment. The WHATWG standard defines how browsers normalise these parts. That normalisation can differ from a hand-written filter, notably for ports, IP addresses, Unicode characters and separators.

The string is not the URL

A filter often sees a string before the HTTP client turns it into a URL. A difference in separators, ports or host parsing can make one destination pass validation while another is contacted. This tool shows the output of the same WHATWG parser used by modern browsers.

Query string and fragment

The query string reaches the server and frequently ends up in logs. The fragment, after #, is not part of the HTTP request, but page JavaScript can read it and the browser keeps it in history. Neither is a vault for secrets.

?Frequently asked questions

Does the tool contact the domain?

No. It only calls the URL constructor supplied by the browser. It does not resolve DNS, follow the link or check whether the host exists.

Why does the canonical form differ from my input?

The parser normalises host casing, default ports, . and .. segments and some encoded characters. Browsers then use that form for origin checks.

Why are some parameters hidden?

An OAuth code, token or secret stays local, but can still appear in a screenshot or copy and paste. The sanitised version is designed for tickets and reports.

+More tools

Technical assessment

Request an application or infrastructure assessment

For an assessment by our team, specify the systems involved, available access and requested tests in your enquiry.