DNS Studio tool

About DKIM Studio

A focused tool for one job: making DKIM — the signatures behind trusted email — clear enough to check, fix, and improve.

DKIM Studio does three things. It checks DKIM records — fetching the record for a selector, decoding the public key, and measuring its strength. It finds selectors when you do not know which names a domain publishes. And it generates new keys entirely in your browser, with the exact TXT record ready to paste into DNS.

It exists because DKIM sits at an awkward intersection: it matters to everyone who sends email, but the tooling around it tends to assume you already speak DNS and cryptography. We think a founder should be able to read “your key is weaker than recommended” and know what to do next, and a deliverability engineer should get the raw record, the parsed tags, and the exact modulus length without fighting the interface. That is what the Easy and Tech modes in the header are for.

How we build it

Tool first

The checker is the page. Results lead with the verdict, and the explanation follows — never the other way round.

Two audiences, one answer

Easy mode gives a plain-English outcome with the next step. Tech mode shows the raw record, parsed tags, and exact key details. Same check, your choice of depth.

Client-side by design

Lookups run in your browser over DNS-over-HTTPS, and generated keys never leave the page. There is no backend to log the domains you check.

Honest measurements

Key lengths are measured from the decoded RSA modulus, not guessed from the record size. Where a value is an estimate, we say so.

One studio. Six focused tools.

DNS Studio builds focused tools for checking DNS, mail authentication, TLS, SSL, and domain trust. dkim.studio is one of six focused tools — each with its own domain, all sharing one design system and one promise: clear tools for trusted domains.

Get in touch

Found a record the checker misreads, or a selector we should add to the sweep? We want to know. Email [email protected] — it reaches the people who build these tools. For how we handle data (short version: we do not collect it), see the privacy policy.