Private URL inspector
Inspect an HTTP or HTTPS URL’s host, path, port, fragment and query parameters in your browser without visiting the destination.
Parsed hostname
Change an input to update the result.
Inputs are processed in this tab. No text, paths or results are sent to our server or saved in an account. Privacy details.
From input to a useful answer.
- 01
Paste one absolute HTTP or HTTPS address.
- 02
Read hostname, path, query pairs and fragment separately.
- 03
Review any stripped copy before sharing or using it.
Read components without visiting the destination
The inspector uses the browser’s URL parser to separate protocol, hostname, port, path, query pairs and fragment. It accepts absolute HTTP and HTTPS URLs, limited to 20,000 characters and 200 query parameters. It does not visit the address or follow redirects.
The parser can normalise the result, so it is not a byte-for-byte forensic record. A normalised address may omit a default port. Hostnames containing an xn-- label are flagged as internationalised representations; that flag alone says nothing about a site’s intentions.
Keep repeated query pairs visible
Repeated keys remain separate entries. In the example, tag=a and tag=b produce two tag rows. Query parsing also applies form-style decoding: q=maple+leaf displays as maple leaf. The site’s separate percent-component decoder instead leaves a plus sign literal.
Embedded username/password credentials are reported as present and redacted in the parsed result. The stripped copy removes them together with all query parameters and the fragment. The original remains in your input, and sensitive text can still occur in a path.
Structure is not a safety verdict
A successfully parsed URL can still lead somewhere unwanted. This tool checks no reputation, ownership, certificate, redirect destination or downloaded content. HTTPS is a protocol choice shown in the result, not a promise that the destination is trustworthy.
Removing query data can change behaviour. A signed download, search result or invitation may depend on its parameters and stop working after stripping. Inspect the copy and decide whether it serves your purpose. Removing the query and fragment does not by itself anonymise the remaining address.
References
MDN — URL API ↗MDN — URLSearchParams ↗RFC 3986 — URI generic syntax ↗A few useful answers
Does this check whether a link is safe?
No. It parses components locally and makes no destination request. There is no reputation or malware verdict.
Why did + become a space in a query value?
URLSearchParams applies form-style query decoding. The separate component decoder deliberately leaves + literal.
Does the stripped copy remove every secret?
No. It removes credentials, query and fragment; remaining components such as the path can still contain sensitive information.