A wildcard answers every DKIM selector, with the key revoked

What it means

Every selector we asked about on example.com returned the same record with an empty p= tag, including one we invented. That is a wildcard publishing a revoked key, and it is the standard way to say this domain signs no mail at all. We checked N selectors and they are one record, not N problems.

How to fix it

Nothing, if the domain is not meant to send mail. If it is, publish a real key at a named selector, because a wildcard revocation tells every receiver to distrust any signature claiming to come from here.

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.1. 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