Skip to content
uencoder
PIPELINE Web Development Beginner 2 steps

Punycode Decode and URL Parse

Punycode encodes internationalized domain names as ASCII. Decoding restores Unicode. URL parsing extracts components.

What it solves

Decode Punycode domain then parse the full URL.

Input → Output

Punycode Decoder input → URL Parser output across 2 steps.

Runs in

1–2 minutes · fully local in your browser.

Before you start

  • A Punycode-encoded domain URL

The pipeline

  1. 1 Punycode Decoder punycode-decode

    Decode Punycode (RFC 3492) text back to Unicode. Free, private, and 100% client-side.

  2. 2 URL Parser url-parser

    Parse a URL into its components: protocol, host, path, query, hash, port, username, and password. Free, private, and 100% client-side.

Open in Toolchain

Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.

▶Run this workflow

Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.

Pipeline progress

  1. Punycode Decoderpunycode-decode
  2. URL Parserurl-parser

Sample input

https://xn--fsq.example.com

Expected output

Protocol:  https:
Username:  
Password:  
Host:      xn--fsq.example.com
Hostname:  xn--fsq.example.com
Port:      
Path:      /
Query:     
Hash:      
Origin:    https://xn--fsq.example.com
Href:      https://xn--fsq.example.com/

This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.

Related workflows

You might also need

Workflows sharing tools or topics with this recipe.

Learn more

Tools used