toolhq helps developers diagnose technical problems quickly without unnecessary data exposure.
It is a debugging toolbox for code, data, APIs, DNS, domains, TLS certificates, email infrastructure and networking. Paste what you have, find out what is wrong, and move on.
how every tool works
- Local when the work can be local: formatting, decoding, hashing and key handling stay on your device.
- Every tool that uses the network says so on the page, and says what it sends, before you type anything.
- No account, no sign up and no API key for the core tools, including the MCP endpoint.
- Nothing you enter into a tool is logged, stored, or passed to analytics.
- Each page is statically generated and usable the moment it paints.
- Tools point at the next check in the task, so a diagnosis does not stall at one lookup.
Why another tool site
Most online utilities are wrapped in ads, popups and trackers, and many quietly send your input to a server you know nothing about. That is a real problem when the thing you are pasting is an API response, a token, a private key, or unreleased work. toolhq exists to be the version of these tools you can use without thinking about it: the work happens on your device wherever it can, and where it genuinely cannot, the page tells you what leaves and where it goes.
The second problem is that debugging is rarely one lookup. Mail going to spam is an MX check, then SPF, DKIM and DMARC, then a blacklist. A certificate error is what the host is serving, then the chain, then revocation. toolhq is built around those sequences, so each tool ends by pointing at the next check in the task rather than a generic list of neighbours.
Who it is for
Developers first: JSON, JWTs, regex, Base64, diffs, API requests, HTTP headers. Then DevOps engineers and sysadmins working on DNS, TLS, certificates, server config, addressing and network diagnostics. Then the people who look after email infrastructure, where SPF, DKIM, DMARC, BIMI, MX and blacklists all have to line up. There are design utilities here too, for colour, contrast, gradients and easing, but they are a small part of the collection rather than the point of it.
There is a fourth audience now: AI coding agents. The checks that need real network access are exposed over the Model Context Protocol, so an agent can look up DNS, read a certificate or check MX records itself instead of guessing.
Who builds this
toolhq is built and maintained by Jameel Haider, a developer who got tired of pasting API responses into tool sites that upload them. Every tool and every guide is written and maintained by him, tested against the real behaviour of browsers, DNS resolvers, certificate authorities and mail servers rather than copied from other reference sites. If a tool feels slow or gets in your way, that is a bug worth reporting.