Pikkola URL, tool No. 59

A link is six parts and a query string.

Paste an address and each part of it lands in its own field. Edit the query as a table and the address is put back together as you type. Tag a campaign, strip what a tracker appended, and see what the three encoders do to the same text. Nothing is uploaded and nothing is stored.

6
parts
3
encoders
0
requests

The studio

Four benches around one address

Each bench keeps its own answer and updates as you type. Nothing moves between them unless you press the button that moves it.

01

Take an address apart

Scheme, host, port, path, query and fragment. The query becomes a table you can edit, sort and reorder, and the address is put back together from those pieces.

Leave the port empty unless the address names one. Browsers hide 80 and 443.

Path segments Removing one joins the rest in order.
Query parameters
Send Name Value Actions
Put back together

Sent to the server

Kept in the browser

02

Build a campaign link

Five fields, one address. Tags already on the base address are replaced instead of doubled, and each value is encoded once.

Presets
Tagged address
    Nothing leaves the tab

    No request, no account, no storage. The Content-Security-Policy sets connect-src to none, so the page could not upload an address even if it tried.

    03

    Strip what a tracker added

    Paste one address per line. The parameters a platform appended are removed and named, and everything else is left where it was.

    A line that is not an address is kept as it is and reported below.

    What to remove
    Cleaned

    04

    The three encoders, side by side

    The same text through encodeURI, encodeURIComponent and a form body. The difference is exactly the characters that decide whether a value survives a server.

    Decode it back
    A domain in another script
    ASCII form

    The browser sends the ASCII form. The readable form is how it is typed, not what arrives.

    CharacterencodeURIencodeURIComponentForm

    What the browser does to an address

    The parts are simple, but the rules behind them are where a link breaks. These are the ones the benches follow.

    • 1
      The fragment never reaches the serverEverything from # onward stays in the tab. A fragment that looks like a parameter is still not a parameter, and a redirect can drop it on the way.
    • 2
      A plus is a space only in a formapplication/x-www-form-urlencoded turns + into a space and a space into +. In a URL's query, a + is a plus. The decode box lets you read either way.
    • 3
      A percent escape is a byte, not a characterEach Korean character is three bytes in UTF-8, so 가 travels as %EA%B0%80. One character can be several escapes, and an escape can be one byte of a character.
    • 4
      The host ignores case, the path does notEXAMPLE.com and example.com name the same host. /Page and /page can be two different files on a server that cares, so the path is kept exactly as typed.
    • 5
      Two parameters with one name are a listThe order is part of what the server sees, and a repeated name is not always a mistake. The table keeps each pair separate and never merges them.
    • 6
      A non-Latin domain travels as punycode한국.example is sent as xn--3e0b707e.example. The readable form is an input method, not what arrives, and DNS never sees the Korean letters.

    Questions

    Is the address sent anywhere?

    No. There is no endpoint to send it to. The page sets connect-src to none in its Content-Security-Policy, which forbids fetch, XMLHttpRequest, WebSocket, EventSource and beacon. Load it once and it keeps working with the network off.

    Does removing tracking parameters break the link?

    The parameters in the list are the ones advertising platforms append, and a page that needs them to render is rare. A parameter the site itself uses, such as a page number or a share token, is in no group and stays. If a site hands out signed links, check the cleaned address once before a campaign.

    Why did a Korean value turn into percent signs?

    A percent escape holds bytes, and each Korean character is three bytes in UTF-8. 가 becomes %EA%B0%80. That is what the server receives. The table shows the readable value and the address it produces, so both are visible.

    Two parameters share one name. Can I edit them separately?

    Yes. Each row is its own pair. The order is kept, and sorting by name keeps the duplicates next to each other instead of merging them into one value.

    How exact is the punycode conversion?

    Encoding uses the browser's own internationalised domain handling, so it matches what the browser would request. Decoding runs in this page. The full UTS 46 mapping table is not applied, so a label with unusual case or a join control can be read differently by a registrar.

    What happens to an address with no scheme?

    It is read as https and the bench says so instead of hiding the assumption. Type a scheme when the address is not https, or when you are testing how a server treats http.