About URL Parser

Break a URL into scheme, host, path, query, fragment. Part of the DevTools Surf developer suite. Browse more tools in the Web / Frontend collection.

Use Cases

• Debugging redirect URLs with complex query parameters
• Extracting individual URL components for routing logic
• Validating URL structure before storing in a database
• Parsing deep links to verify scheme and path segments

Tips

• Paste a full URL to see scheme, host, path, query, and fragment
• Identify query parameters at a glance in the parsed output
• Use this to debug malformed URLs in API integrations

Fun Facts

• The URL specification (RFC 1738) was published by Tim Berners-Lee in December 1994, defining the format that billions of people use daily.
• The maximum practical URL length is about 2,048 characters in Internet Explorer, though the HTTP spec (RFC 7230) imposes no limit.
• The '#' fragment identifier in URLs is never sent to the server — it is processed entirely by the client browser, a design choice from the original spec.

FAQ

What parts does it extract?

Scheme, host, port, path, query, fragment. Plus subdomain vs domain vs TLD separation when possible.

Does it handle punycode?

Yes — international domain names (例え.jp) are shown in both Unicode and punycode forms. Browsers and DNS use punycode internally.

What about authentication in URLs?

user:password@host notation is parsed. The tool warns that this is deprecated for security — use proper HTTP auth instead.

Is it safer than JS's URL?

Uses the same WHATWG URL parser (via the native URL constructor). Behavior matches modern browsers exactly.