Multiple DKIM records at {selector}

What it means

N TXT records answer at selector1._domainkey.example.com. Verifiers cannot tell which key is yours and may pick the wrong one, so verification becomes a coin toss.

How to fix it

Keep exactly one TXT record at that selector and delete the rest. It is usually a leftover from a provider migration.

Check your own domain

This page describes the condition. To find out whether your domain has it, run the DKIM test or the full checkup, which examines every record at once.

Understand it properly

This page covers one condition. For the whole picture, What is DKIM, selectors and key strength, or start at the Health Library.

Where this comes from

We judge this against RFC 6376 section 3.6.2.2. Every finding on this site cites the specification behind it so you can check the work rather than take our word for it.

Other DKIM conditions

• No DKIM key found at the usual selectors
• No DKIM key at the selector you gave
• DKIM key at {selector} has been revoked
• DKIM key at {selector} is below the minimum size
• DKIM key at {selector} is only 1024 bits
• DKIM key at {selector} is restricted to SHA-1