DKIM signs each message you send, and receivers check the signature against a public key in your DNS. When mail lands in spam with a DKIM failure, the question is always the same: what changed, and where. This tool verifies every signature on a real message, says in plain words why each one passes or fails, and checks the ARC chain that forwarders add.
How to use it
Save the message as an .eml file (most mail programs offer "Save as" or "Download original") and upload it, or open the original and paste all of it, headers and body. Uploading is safer: a copy through a browser can change line endings or trailing spaces and break the body hash. If the pasted text has bare line breaks, we turn them back into the form mail uses and say so in the result.
What we check for each signature
- The signature itself: the signing domain and selector, the algorithm (RSA with SHA-256 or SHA-1, or Ed25519), the canonicalization, the signed headers, and the signing and expiry times.
- The key: we look it up at
<selector>._domainkey.<domain>, report its type and size, and say when it is missing, revoked, malformed, too short or in testing mode. - The body hash: whether the body still matches what was signed. A mismatch means something changed the body, often a footer added by a list or gateway.
- The signature: whether it verifies against the key. A mismatch means a signed header changed or the key in DNS isn't the one that signed.
- Alignment: whether the signing domain matches the From domain, which DMARC needs.
The result lists every signature with its verdict and the reason, and the findings say what to fix. Up to 10 signatures are verified per message.
The ARC chain
When a forwarder or mailing list changes a message, the original DKIM signature breaks. ARC lets that forwarder seal the authentication results it saw before the change. We check the chain's structure, verify each seal and the newest message signature, and say whether the chain holds or where it breaks. You can turn this off under More options.
Pasted mail stays private
The message is processed in memory and discarded when the answer is sent: never cached, stored, logged, streamed, shared or repeated in an error. The result keeps only domains, selectors, header names and verdicts. It never holds the Subject, an address before its @, a header value or the body.
Verification in our own code
We verify signatures with our own implementation of the DKIM and ARC standards, built on a widely used cryptography library, and test it against an independent DKIM library and the published Ed25519 test vectors. Key lookups go through our own resolver, at most 20 per message.
Reading the reasons
Each signature gets one of four results. Pass means the key, the body hash and the signature all check out. Fail means the cryptography or the expiry said no: the body or a signed header changed, or the signature has expired. A temporary error means the key lookup didn't answer, so the result may change if you try again in a minute; the result is then marked partial. A permanent error means the signature or its key can't be used at all, for example a key that is missing, revoked, malformed or too short, or an algorithm receivers don't support. Warnings such as SHA-1, a 1024-bit key or a body length limit sit next to a pass: the signature works today, but it is weaker than it should be.
When a signature fails
Every failure links to a guide. A changed body usually means a footer or a link-rewriting gateway; a changed header often means a tagged Subject. A missing key usually means a new sending service whose DNS records were never published. Check a key on its own with the DKIM record validator, and read where a message travelled with the email header analyzer.