Why won't this relative path parse as a full URL?

Relative references like `/settings` or `../api` need a base URL. They are valid in context, but they are not absolute URLs on their own.

Why did the port disappear from the parsed output?

Browsers often normalize default ports away. `:80` for `http:` and `:443` for `https:` may be omitted in the serialized form even if they were present in the input.

Why did the hostname change case?

Hostnames are case-insensitive, so browser parsers usually normalize them to lowercase.

Why is the fragment not included in my request debugging?

The hash portion after `#` stays client-side and is not sent in normal HTTP requests.

Why do encoded characters still appear in some fields?

Some characters remain percent-encoded depending on context and serialization rules. A parser may decode query parameter values for inspection while preserving encoded form in the raw URL fields.

URL Parser / Inspector

Parse an absolute URL with the browser URL API, inspect normalized parts, and review decoded query parameters locally.

URL input

Absolute URLs only

This inspector uses the browser URL constructor without a base URL. Relative inputs like /docs are rejected on purpose so parsing behavior stays explicit.