Domain check / DKIM

<DKIM>

DomainKeys Identified Mail

DKIM puts a digital signature on every email. That lets recipients check whether the message really comes from your domain and has not been altered along the way. Does the signature check out? Then your email arrives with more trust. Does it not? Then fraud is stopped.

<why it matters>

Why DKIM matters

DKIM puts a digital signature on every email. The recipient fetches the matching public key from your DNS and checks whether the email really comes from your domain and has not been altered along the way.

Unlike SPF, a DKIM signature stays valid when an email is forwarded. That makes DKIM, in practice, often the check that makes DMARC pass.

Every service that sends on your behalf has to sign with your domain: Microsoft 365, your newsletter service, your CRM and your accounting software. If a service signs with its own domain, that does not help your DMARC.

<example>

What a DKIM record looks like

selector1._domainkey.yourdomain.com (TXT)

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…
PartWhat it means
selector1The selector: the name of this key. Every service has its own selector, so you can have several keys side by side.
_domainkeyFixed name under which DKIM keys live in your DNS.
v=DKIM1This is a DKIM key.
k=rsaThe key type.
p=…The public key. With Microsoft 365 you do not publish a key yourself, but two CNAME records that point to Microsoft.
<in order>

DKIM done right

  • Every service that sends on your behalf signs with its own DKIM key.
  • The public key is in your DNS under a selector, for example selector1._domainkey.
  • Keys are long enough (2048 bit) and are replaced from time to time.
<common problems>

What goes wrong, and what you can do

DKIM is not enabled for your own domain in Microsoft 365

By default, Microsoft 365 signs with your onmicrosoft.com domain, not with your own domain. You have to enable DKIM yourself: add the two CNAME records selector1 and selector2 to your DNS, and enable DKIM in the email authentication settings in Microsoft Defender.

A service signs with its own domain

Many newsletter and CRM services sign with their own domain by default. DKIM then passes, but the domain does not match your sender address, and DMARC fails. Set up domain authentication at that service, so it signs with your domain.

A key that is too short

A 1024-bit key is considered too weak. Use 2048 bit. Some DNS providers cannot store such a long value in one go; you then split it into several strings within the same TXT record.

Old keys and selectors

Keys of services you no longer use often stay in your DNS for years. Remove them. Rotate active keys from time to time. Microsoft 365 does that itself with its two selectors.

<together with DMARC Advisor>

We take it off your hands

Brandaris works with DMARC Advisor, the Dutch DMARC specialist that has been around since 2013. In the DMARC Manager reports we see for each service whether the DKIM signature is valid and matches your domain. That way we quickly find which service still signs with its own domain, and we fix it together.

<frequently asked questions>

About DKIM

Is your question not listed? Call us on 072 202 97 95.

What is a DKIM selector?

The name of a key. Every service uses its own selector, such as selector1 for Microsoft 365. That lets several services sign with your domain side by side.

How often should I replace DKIM keys?

There is no fixed rule. Many organisations rotate once a year. Microsoft 365 handles it itself with its two selectors.

Can I have several DKIM keys?

Yes. Every service gets its own selector and key. That is exactly the idea.

Why does DMARC fail while DKIM passes?

Then the service probably signs with its own domain instead of yours. DMARC requires the domain in the signature to match your sender address.

<newsletter>

Our newsletter

Cybersecurity is not just technology. It is people work. In our newsletter we share knowledge, stories and experiences that show how we help organisations move forward. The newsletter is in Dutch.