Tools

Developer & network tools,
no nonsense.

Free tools for the things you check ten times a week: DNS records, SSL certificates, email authentication, HTTP headers and redirects, who owns an IP, and the usual encode, decode and format jobs. One page each. No sign-up, no tracking, nothing stored. The server-side ones answer in plain text for curl and JSON when you ask for it.

New

Domains & email

What the world sees when it looks up your name: DNS records, SSL/TLS certificates and mail policy.

HTTP & debugging

Watch requests go in and come out. Point things at these while you debug.

Addresses & networks

Who owns an address and how traffic reaches you.

Encode & decode

Runs entirely in your browser. Nothing you paste leaves the page.

Guides

Short, first-hand explanations of the things these tools show you. All guides.

How these tools work

Everything is served by one small Go binary with no database. Server-side tools (DNS, SSL, email, HTTP, ASN) make real network requests from this server and show you exactly what came back; browser-side tools (JSON, JWT, Base64, timestamps, diff, hashes) run entirely in your browser and never send your data anywhere. Nothing you look up is logged or stored: there is no access log, and the only record kept is an anonymous count of how many times each tool was used (see Privacy).

Server-side tools pick their output format from ?format=html|text|json, then the Accept header, then the user agent. curl, wget and httpie get plain text by default, so every tool doubles as a small API. None of them needs an API key, and reasonable automated use from scripts and CI is welcome within the rate limits (see Terms). The API and curl reference lists every endpoint, its parameters and JSON fields, with ready-made checks for CI. Outbound lookups are rate limited per visitor and only ever target public addresses.