Contact
Bug reports, feature requests, "this URL broke the parser" stories, and "the encoder mangled my fragment" reports are all welcome. The fastest way to get my attention is email, with a sample URL (or short list) attached — one I can paste straight back into the tool to reproduce.
Reporting a bug
A useful bug report has three things: (1) the URL of the tool page you used, (2) what you expected vs. what happened, and ideally (3) the input that triggers it. URLs paste into email cleanly — please include them raw rather than as screenshots.
Anything you send me in email is fair game for reproducing the bug and nothing else. If a URL contains a token, session ID, or anything else sensitive, please redact or synthesize an equivalent; the privacy policy on the site only covers what happens in the browser, not what you choose to send me directly.
Requesting a tool
Before suggesting a new URL tool, check the homepage and the footer to make sure it's not already there in slightly different form. The 30 tools here cover the URL operations I personally reach for; the bar for adding more is "useful enough that I'd reach for it again next month."
What this site doesn't do
It does not fetch your URLs — CORS in the browser blocks cross-origin
requests to most useful targets, and pretending to "follow redirects" or "preview Open
Graph metadata" would just succeed half the time and fail unpredictably the rest. Where
a server is genuinely required (live redirect chain following, real OG fetch, AASA /
assetlinks validation), the relevant tool emits a one-line curl command you
can run on your terminal instead. Each of those gaps is deliberate, not an oversight.
Other sites
Sister tools for adjacent file formats: csvkit.org (CSV), jsonlkit.com (JSONL / JSON Lines), pngtoolskit.org (PNG), pdftoolskit.org (PDF), tomlkit.org (TOML), geojsonkit.org (GeoJSON). Same browser-only philosophy.