Skip to content

DKIM

DomainKeys Identified Mail adds a cryptographic signature to each message so receivers can verify the sender's domain and that the content was not altered.

With DKIM, the sending server signs selected headers and the body of each message with a private key. The matching public key is published in DNS as a TXT record at a name made of a selector, the label _domainkey and the domain. The selector lets a domain hold several keys at once, for example one for each sending service.

A receiver reads the selector from the message's signature header, fetches the public key and checks the signature. A valid signature shows that the message was signed by a party controlling that domain's DNS and that signed parts were not changed in transit. Because the signature travels with the message, DKIM usually survives forwarding.

Common problems are a selector that was never published, keys that were rotated without updating DNS, and sending services that sign with their own domain instead of yours. A DKIM check needs the selector, so tools that scan a domain usually try common selectors.

[ Validate ][ Enrich ]
[Get started]

Run your first lookup in two minutes

Create a key, pick a plan and call any product in the catalog. Plans start at $29 a month.

[ Screen ][ Scrape ]