Analizador de URL

Pega una URL y ve cada parte desglosada: esquema, host (dividido en subdominio / dominio / TLD, con detección IPv4 / IPv6 / IDN), puerto, segmentos de ruta, parámetros de query y fragmento. Modifica cualquier campo y la URL reconstruida se actualiza en vivo. Puramente del lado del cliente, sin subir nada, sin rastreo.

Probar:
Cómo funciona el análisis de URL aquí
  • El analizador sigue RFC 3986: esquema, luego //, luego userinfo (user:pass@ opcional), host, :puerto, ruta, query, fragmento.
  • Los hosts se clasifican: IPv4 (p. ej. 192.0.2.1), IPv6 entre corchetes (p. ej. [2001:db8::1]) o un nombre DNS. Los nombres DNS que contienen una etiqueta xn-- se marcan como IDN (Nombre de Dominio Internacionalizado en forma punycode).
  • Los hosts en rangos privados / loopback (RFC 1918 IPv4, ::1, link-local fe80::/10, ULA fc00::/7) se marcan en el desglose.
  • Los puertos se asignan a su nombre de servicio común cuando se conocen — 22 → SSH, 5432 → PostgreSQL, 27017 → MongoDB, y así sucesivamente. Un puerto que no coincide con el predeterminado del esquema se marca.
  • Los segmentos de ruta y las claves de query se muestran decodificados (UTF-8). La forma codificada original se conserva para el round-trip.
  • "Parece phishing" se activa cuando (a) hay userinfo presente, (b) un parámetro de query parece password= / passwd= / token=, o (c) el fragmento parece un ancla de página de inicio de sesión. Es una heurística, no un veredicto.
  • La reconstrucción "canónica" pone esquema + host en minúsculas, elimina el puerto predeterminado (p. ej. :443 en https://) y ordena la query alfabéticamente.
  • No se sube nada. Todo se ejecuta en tu navegador.

About this tool

URL Parser decomposes any URL into its component parts — scheme, user info, host, port, path, query string, fragment — and decodes percent-encoded characters in each part. It also parses the query string into a key/value map, handles duplicate keys (they become arrays), and lets you copy any part to the clipboard. The parser follows the WHATWG URL standard, which is the same algorithm browsers use in the address bar — so what you see is what the browser will see when it navigates to the URL.

When to use it

  • Inspecting a long URL with many query parameters before sharing it in a ticket or a chat
  • Debugging a redirect by seeing how the path and query change across hops
  • Decoding a percent-encoded URL to see the original characters
  • Extracting specific parameters from a URL for use in a script

When not to use it

  • You need to fetch the URL — this tool parses, it does not request. Use curl or a browser to fetch
  • You need to construct a URL safely — use the URL Builder tool on the site, which percent-encodes components correctly
  • You need to follow redirects — the parser shows the URL you gave it, not the final URL after redirects

Frequently asked questions

What standard does it follow?

The WHATWG URL standard, which is the same algorithm modern browsers use. URLs that the parser accepts will navigate correctly in Chrome, Firefox, Safari, and Edge. Legacy RFC 3986 quirks (such as a path that starts with a double slash being treated as protocol-relative) are handled the same way the browser handles them.

What happens with non-ASCII characters in the URL?

The parser preserves the percent-encoded form for the canonical representation, and shows the decoded form alongside so you can see the original characters. The two are equivalent — the browser will treat them as the same URL.

← Back to the homepage · More guides · More from the blog