ThreatPort Feature

Free DKIM Record Checker

Look up your DKIM selector and see whether your domain publishes a signing key. No account required.

DKIM is the half of email authentication that survives forwarding, and it is the half most often left unconfigured. A domain with SPF and DMARC but no DKIM passes authentication only while the message travels directly — the moment a mailing list or a forwarding rule touches it, SPF breaks and there is no signature to fall back on.

  • No DKIM key published, so forwarded mail fails authentication

  • A selector configured at the provider but never added to DNS

  • DMARC at p=reject with only SPF aligned, which silently drops forwarded mail

  • A key rotated at the provider while DNS still publishes the old one

  • How ThreatPort solves this

    ThreatPort probes the selectors mail providers use by convention and reports whether a signing key is published for the domain. Because a selector can be any string, a domain using a custom one may show as not found here while working correctly — the check tells you where it looked rather than asserting a negative it cannot prove.

    Common DKIM selectors probed in public DNS
    DMARC policy and SPF record read in the same pass
    MX records listed so you can see which provider signs
    TLS certificate validity and expiry
    No signup, no email

    Frequently Asked Questions

    Why does the check say no DKIM when I have it configured?

    A DKIM selector can be any label the sender chooses, and there is no way to enumerate them from DNS. This check probes the selectors that major providers use by convention. A domain using a custom selector will show as not found even though signing works, which is why the result says the selector was not found at the common names rather than claiming DKIM is absent.

    What breaks if DKIM is missing?

    Forwarded mail. SPF authorises the sending server, so when a mailing list or a forwarding rule relays a message the original server is no longer in the path and SPF fails. A DKIM signature travels with the message and still validates. Without it, a domain at DMARC p=reject can have legitimate forwarded mail rejected.

    How often should keys be rotated?

    Providers differ, and rotation matters less than making sure DNS matches what the provider is signing with. The common failure is rotating at the provider and leaving the old public key in DNS, after which every signed message fails validation until the record is updated.

    Is DKIM enough on its own?

    No. DKIM proves a message was signed by a key published for the domain, but nothing instructs receivers on what to do when validation fails. That instruction is DMARC. SPF, DKIM and DMARC are checked together here because a gap in any one of them leaves the domain spoofable in a different way.

    Start in minutes

    No agents. No configuration. No professional services.

    $50 per domain per month — cancel anytime.

    Compared to enterprise ASM platforms that require a sales call for pricing.

    We use essential cookies to operate this site and optional analytics cookies to improve it. Cookie Policy