URL Parser

A URL parser separates an address into components such as scheme, username, host, port, pathname, search parameters, and fragment. Each component has different security and routing implications. A query parameter is not the same as a path segment, and a fragment is not sent to the server in an HTTP request. Parsing the structure first makes redirects, callback URLs, and API endpoints easier to reason about.

Paste a URL and verify the scheme, effective hostname, port, and encoded values before opening it or using it in a redirect. Watch for userinfo before the host, look-alike Unicode characters, repeated parameters, and percent-encoded delimiters. Treat parsed values as untrusted input and validate allowed origins on the server. A parser explains what the browser sees; it does not make an arbitrary redirect safe.

Callback URLs, signed links, and diagnostic traces often contain tokens or identifiers that should not leave the developer's session. Local parsing provides immediate visibility without sending the full address to a third party. For production code, use the platform URL API and test canonicalization, duplicate keys, internationalized domains, and path traversal boundaries. Keep the utility focused on inspection and enforce trust decisions in the application that consumes the URL.