Skip to tool
Web engineering

URL Inspector & Query Editor

Separate, edit, encode, and rebuild every URL component.

Web Worker Local onlyTools
Input0 characters
Result0 characters
Ready

Parse precisely · normalize intentionally

A URL can keep its meaning while changing its bytes.

Browsers parse, normalize, encode, and serialize. That is useful—until a cache key, signature, duplicate parameter, or audit log depends on the spelling you started with.

Raw ink · copied byteshttps://User:pa%24%24@例子.test:8443/a%2Fb/c%20d?tag=red+shoes&tag=web#Top%2FSection
Normalized glass · platform serializationhttps://User:pa%24%[email protected]:8443/a%2Fb/c%20d?tag=red+shoes&tag=web#Top%2FSection

Hostname normalization is visible. Credentials, query order, and escaped path separators deserve review before reuse.

URL anatomy rail

Each delimiter changes the parser state.

Schemehttps:

Security and default-port context

CredentialsUser:••••@

Frequently logged or leaked

Hostxn--fsqu00a.test

IDN serializes as ASCII

Port8443

Non-default origin member

Path/a%2Fb/c%20d

%2F stays inside a segment

Query?tag=…&tag=…

Ordered key/value pairs

Fragment#Top%2FSection

Client-side; not sent in HTTP requests

Query as ordered multimap

Duplicate keys are first-class data.

Object conversion would overwrite tag=red shoes with tag=web. URLSearchParams keeps both pairs in order.

01tagred shoesplus decoded as a space
02tagwebsame key, second value
03empty∅empty value
04flag∅key-only spelling normalizes
05next/billing?step=2nested URL value

Encoding courtroom

The same glyph can carry different protocol meaning.

Spacered shoesred%20shoes

red+shoes in form-style query data

Literal plusC++C%2B%2B

A raw + may decode as space

Path slasha/ba%2Fb

Escaped slash stays inside one segment

Unicode host例子.testxn--fsqu00a.test

IDNA hostname serialization

Percent sign50%50%25

Double encoding would create %2525

Secret-bearing URL triage

Readable does not mean safe to log.

Credentials

HIGH

Strip userinfo before sharing or logging.

Access token query

HIGH

Prefer headers; query strings spread through logs and history.

Signed parameters

BYTE-SENSITIVE

Normalization or reordering can invalidate a signature.

Fragment data

CLIENT-SIDE

Not sent in HTTP, but can still leak through copied links and scripts.

Rebuild diff

Inspect the bytes created by one logical edit.

Only the final byte changed here. Re-run the comparison after sorting, decoding, IDN normalization, or component edits.

Before?tag=red+shoes&tag=web&next=%2Fbilling%3Fstep%3D2
After · one byte edited?tag=red+shoes&tag=web&next=%2Fbilling%3Fstep%3D3

Direct answer

What is URL Inspector & Query Editor?

Parse URL components and repeated query parameters locally, compare raw input with platform serialization, and expose encoding changes before rebuilding a URL.

What can it do?

  • Inspect
  • Normalize
  • Encode
  • Decode
  • Resolve

How to use URL Inspector & Query Editor

  1. 01

    Choose a task

    Select Inspect, Normalize, Encode, Decode, and Resolve in the workspace.

  2. 02

    Provide the input

    Paste a complete or relative URL. The input stays in the browser processing path.

  3. 03

    Review the result

    Run the tool, inspect its result and diagnostics, then copy or download the output when the page offers that action.

Frequently asked questions

What is URL Inspector & Query Editor?
Parse URL components and repeated query parameters locally, compare raw input with platform serialization, and expose encoding changes before rebuilding a URL.
What can URL Inspector & Query Editor do?
URL Inspector & Query Editor supports Inspect, Normalize, Encode, Decode, and Resolve. Each mode is available directly in the page workspace.
Does URL Inspector & Query Editor upload my data?
URL Inspector & Query Editor processes your input locally in the browser. DevSexy does not add an upload, account, or server-processing step to this workflow.
DevSexy processes tool input locally. No paste tracking, accounts, or upload step.