How to use it
- 1
Paste a full HTTP/HTTPS URL.
- 2
Compare the normalized and request URLs.
- 3
Verify slash and query semantics separately against the server.
What the tool can do
- Normalizes scheme and hostname casing, default ports, and IDNA serialization.
- Resolves dot segments and normalizes percent encoding without decoding reserved characters.
- Shows the fragment-free request URL and preserves query order.
Common use cases
- Compare URLs before configuring a redirect or canonical.
- Review IDNs, default ports, and ambiguous percent encoding.
- Prepare consistent URLs for a migration spreadsheet.
How it works inside
The result uses the browser URL parser and makes no network request.
Query order is preserved because backend semantics can depend on order and repeated keys.
Questions and answers
Can every URL be replaced with the normalized form automatically?
No. Duplicate slashes, trailing slashes, parameter order, and application routing must be checked against the real server.
Is this a canonical checker?
No. It analyzes one URL's syntax; canonical intent is checked separately on the published page.
