Free URL parser and query parameter inspector. Inspect URL components, protocol, host, path, parameters, and hash fragments with instant live editing.
Loading tool...
The URL Parser & Query Inspector is a fast URL inspect tool and URL inspector that decomposes web URLs into RFC 3986 components (Protocol, Host, Port, Path, Query, Hash), features an interactive query parameter editor with live URL reconstruction, canonical normalization mode, and automated security vulnerability checks.
Parses URLs using standard W3C URL and URLSearchParams APIs. Offers an interactive editor to add, edit, delete, and sort query parameters in real time with live URL reassembly. Includes a canonical normalization engine (strips tracking UTM tags, normalizes trailing slashes, downcases hostnames) and a heuristic security scanner that flags unencrypted HTTP, credentials in URLs, open redirects, exposed tokens, and punycode lookalike domains.
https://shop.example.com:8080/products/shoes?category=running&sort=price_asc&utm_source=google#reviewsProtocol: https: | Host: shop.example.com:8080 | Path: /products/shoes
Params: { category: "running", sort: "price_asc", utm_source: "google" }
Hash: #reviewsExtracts every structural layer and presents query parameters as an editable key-value dictionary.
Paste any web link into the URL inspect box. The tool breaks down the protocol, domain, path, hash, and every individual query parameter into an editable table, allowing you to inspect headers, flags, and parameter values instantly.
Yes! The interactive parameter editor lets you add, modify, re-order, and delete query parameters. The full URL regenerates dynamically in real time and can be copied or loaded with one click.
URL normalization converts URLs into a canonical format by lowercasing scheme and hostname, stripping redundant default ports (80/443), and sorting query parameters to maximize cache hits and eliminate SEO duplicate content.
Passing authentication tokens, API keys, or passwords inside URL query strings is an OWASP security risk because URLs are frequently recorded in plaintext web server access logs and browser history.