WSS
Web Specification Studio Home

URL Parser, SSRF Auditor & Differential Inspector

Interactive WHATWG URL parser, normalization inspector, SSRF IP-evasion auditor, query secret scanner, and RFC 8252 OAuth redirect validator.

Target URL Inspector

Preset:

WHATWG URL Standard Components

ComponentNormalized ValueSpec Rule
Originhttps://api.example.comWHATWG §4.2
Protocolhttps:Scheme
Hostnameapi.example.comHost parser
Port(stripped: default port 443)Default Port Stripping
Pathname/v1/checkoutPath segments
Hash / Fragment#step-2Client-only

Query Parameters & Data Leakage Scanner

KeyValuePrivacy / Security Status
tokensec_987123Secret Leak Hazard
planenterpriseClean
user_id10492Clean

SSRF & IP Evasion FindingsNo SSRF Hazards

No integer/hex encoded IP addresses, metadata endpoints, or userinfo authority confusions detected.

RFC 8252 OAuth Redirect ComplianceCompliant

URL satisfies RFC 8252 requirements for OAuth 2.0 authorization redirects.

Code Snippet Exporter

// TypeScript / Node.js WHATWG URL
const target = new URL("https://api.example.com:443/v1/checkout?token=sec_987123&plan=enterprise&user_id=10492#step-2");
console.log("Origin:", target.origin);
console.log("Path:", target.pathname);
console.log("Params:", Object.fromEntries(target.searchParams));

WHATWG URL Standard & Security FAQ

Why do WHATWG URLs strip default ports like 80 and 443?

Under Section 4.3 of the WHATWG URL Standard, 'special schemes' (http, https, ws, wss, ftp) have default ports (80, 443, 21). When a URL authority explicitly specifies its scheme's default port, the parser normalizes and removes the port component from the serialized URL and origin.

What is an SSRF Parser Differential?

Server-Side Request Forgery parser differentials occur when a front-end gateway or security filter parses a URL differently than the back-end HTTP client (e.g., Python urllib vs Go net/url vs cURL). Discrepancies in handling decimal IPs (2130706433) or @ userinfo confusion allow attackers to bypass allowlists.

Why should sensitive tokens never be passed in URL query parameters?

Query parameters are routinely logged in plaintext across proxy logs, CDN request access logs, browser history, and HTTP Referer headers sent to external third parties. PCI-DSS and HIPAA frameworks forbid transmitting secrets or PHI in URLs.

Why does RFC 8252 forbid wildcards in OAuth redirect URIs?

Wildcards in OAuth redirect URIs enable open-redirect and subdomain takeover attacks. An attacker who controls any subdomain under a wildcard pattern (*.example.com) can intercept authorization codes and hijack user accounts.

Try: