DKIM record checker
Enter your domain and, if you know it, your DKIM selector: the checker reads each key it finds, checks its type and size against RFC 8301, and checks SPF and DMARC alongside. Without a selector, it tries 12 names widely used mail services publish their keys under.
Check a domain
DKIM
Your DKIM keys, under your selectors or 12 common ones, with the type and size of each key.
SPF
Your SPF record and every record it includes, its DNS lookups against the limit of 10, and its policy for other servers.
DMARC
The DMARC record that applies to your domain, its policy, its reports and where it comes from.
What a DKIM record does
DKIM signs each message your service sends with a private key, and publishes the matching public key in your DNS. A receiving server fetches that key and checks the signature: the message comes from a server that holds your key, and nothing in it changed on the way.
Each key is a TXT record at selector._domainkey.yourdomain, where the selector is a name your sending service picks, such as google or s1, and writes into every signature as s=. A domain can publish several keys, one per service, and a record with an empty p= is a revoked key.
DKIM is the check that survives forwarding, since the signature travels with the message. That makes it the safer half of DMARC: RFC 9989 asks a domain that publishes p=reject to sign its mail with DKIM.
How the check reads your domain
- Every query goes through PricklyMails' own resolver, never a public one, with at most 32 queries and 8 seconds per check; a section the budget cut short says so.
- SPF follows RFC 7208: one record at the domain, every
includeandredirectfollowed, the lookups counted against 10 and the lookups that find nothing against 2, as receivers count them. - DMARC follows RFC 9989, which replaced RFC 7489 in May 2026: the record at the domain or, without one, the record the DNS walk finds above it, the obsolete
pct,rfandritags noted, and each report address on another domain checked for the authorization RFC 9990 asks for. - DKIM follows RFC 6376, with the key rules of RFC 8301 and RFC 8463: the type of each key, its RSA size, and its flags. Selectors cannot be listed from the DNS, so without yours the check tries 12 common ones.
- The answer is kept 4 minutes, so a second check of the same domain costs no query, then forgotten: no domain is stored, logged or sent to analytics.
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures (opens in a new tab)www.rfc-editor.org
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM (opens in a new tab)www.rfc-editor.org
- RFC 8463: A New Cryptographic Signature Method for DKIM (opens in a new tab)www.rfc-editor.org
- DKIM2 specification, an IETF draft (opens in a new tab)datatracker.ietf.org
- Email sender guidelines (opens in a new tab)support.google.com
- Sender best practices (opens in a new tab)senders.yahooinc.com
Frequently asked questions
How do I find my DKIM selector?
Open a message your domain sent, show its original or raw source, and find the DKIM-Signature header: the selector is the value of its s= tag, and the domain the key lives under is its d= tag. The settings of your sending service usually show it too. Selectors cannot be listed from the DNS, which is why the checker can only try common names when you give none.
What DKIM key size should I use?
A 2048-bit RSA key. RFC 8301 requires at least 1024 bits and recommends 2048, and verifiers must refuse a key under 1024; Gmail and Yahoo recommend 2048 too. Verifiers must handle keys of up to 4096 bits, not beyond. An Ed25519 key is shorter and as strong, but publish it beside an RSA key, under another selector.
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM (opens in a new tab)www.rfc-editor.org
- Email sender guidelines (opens in a new tab)support.google.com
- Sender best practices (opens in a new tab)senders.yahooinc.com
What does a revoked DKIM key mean?
A key record with an empty p= tells receivers the key is withdrawn: any signature made with it fails. It is how a domain retires a key it no longer uses. If your service still signs with that selector, its mail fails DKIM: publish its current key, or switch the service to another selector.
What about DKIM2?
DKIM2 is an IETF draft, not yet a standard, meant to make signatures survive forwarding and mailing lists. Its drafts keep keys where DKIM keeps them, under _domainkey and with v=DKIM1, so a key this checker passes today stays usable under DKIM2 as drafted. The checker adds no DKIM2 test until the standard is published.
- DKIM2 specification, an IETF draft (opens in a new tab)datatracker.ietf.org
- RFC 8463: A New Cryptographic Signature Method for DKIM (opens in a new tab)www.rfc-editor.org
Check your list before your next send.
1,000 tokens free when you sign up, no credit card. After that, you only pay for answers.