Skip to main content
New SPF lookups must resolve in milliseconds — why a DMARC tool's add-on isn't enough Learn Why → →

Free DKIM Record Lookup

Auto-discover DKIM records across 50+ common selectors, or look up a specific selector. Identify which email services sign messages for your domain.

No signup required - auto-discovers SendGrid, Google, Microsoft 365, and 100+ providers

Scans common DKIM selectors via DNS-over-HTTPS to discover which email services sign messages for your domain.

What is a DKIM Record?

A DKIM (DomainKeys Identified Mail) record is a DNS entry that enables email senders to sign outgoing messages with a unique cryptographic signature. This signature acts as a digital fingerprint, allowing recipients to verify that an email genuinely originated from the claimed domain and hasn't been altered in transit.

Think of it like receiving a letter sealed with a wax stamp - the stamp indicates the letter is authentic and hasn't been tampered with during its journey. As of 2023, approximately 80% of Fortune 500 companies use DKIM to secure their email communications.

Authentication Flow

How DKIM Authentication Works

1

Generate Key Pair

A DKIM generator creates a private key (kept secret on your mail server) and a public key (published in your DNS).

2

Sign Outgoing Emails

Your mail server uses the private key to create a unique encrypted signature for each outgoing email, added to the header.

3

Verify on Receipt

The receiving server retrieves your public key from DNS and verifies the signature. If it matches, the email is trusted.

Troubleshooting

Common DKIM Issues

Misconfigured DNS Records

Typos or incorrect entries in TXT records are the most common cause. Double-check for missing quotation marks and proper formatting.

Selector Mismatch

Ensure the selector configured on your mail server matches exactly what's in your DNS record. Even minor discrepancies cause failures.

Key Length Incompatibility

Modern security standards recommend 2048-bit keys. If you're using an older system, verify it supports your chosen key length.

DNS Propagation Delays

After making DNS changes, allow several hours for propagation before testing. Changes don't take effect instantly across all nameservers.

Why It Matters

Why Use the Free DKIM Lookup?

Auto-Discovers Your Selectors

DKIM records hide behind selectors that vary by provider. This tool scans 50+ common selectors so you find SendGrid, Google, Microsoft 365, Mailchimp, and more without knowing the name in advance.

No Selector Guesswork

Not sure which selector a service uses? The auto-discovery does the hunting, and you can still look up a specific selector directly when you know it.

Checks Key Strength

It surfaces the published public key and flags weak 1024-bit keys so you can upgrade to the 2048-bit standard receivers now expect.

Free and Instant

Live DNS results, no signup, and nothing installed - see exactly which services are authorized to sign mail for your domain.

How DKIM Lookups Work

Understanding DKIM Records and Selectors

Unlike SPF or DMARC, a DKIM record isn't published at a single, predictable location - it lives under a selector. That is what makes DKIM lookups tricky, and what this tool automates.

How a DKIM Lookup Works

A DKIM public key is published as a TXT record at selector._domainkey.yourdomain.com. To look it up you need two things: the domain and the selector. The selector is a label chosen by whichever service signs your mail, so a single domain can have several DKIM records - one per sending service - each under a different selector.

Finding the Right Selector

The selector appears in the DKIM-Signature header of any signed message from your domain, as the s= tag. If you can open a sent message's raw headers, that's the surest way to find it. If you can't, the auto-discovery scans the selectors providers commonly use, for example:

  • Google Workspace - google
  • Microsoft 365 - selector1 and selector2
  • SendGrid - s1 and s2
  • Mailchimp - k1

Reading a DKIM Record

A DKIM record looks like this:

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GN...

The v=DKIM1 tag identifies it, k=rsa is the key type, and p= is the base64-encoded public key receivers use to verify signatures. An empty p= means the key has been revoked. The receiving server fetches this key, checks it against the signature on the message, and passes DKIM only if they match and the message wasn't altered in transit.

What a DKIM Check Confirms

  • The key is published at the expected selector and isn't revoked.
  • The key is strong enough - 2048-bit is the modern standard; 1024-bit keys should be rotated up.
  • The record is well-formed, with no stray characters that would break verification.

DKIM, SPF, and DMARC Work Together

DKIM proves a message wasn't altered, SPF proves the sending server is authorized, and DMARC ties both to your visible From address and sets the enforcement policy. DMARC can pass on DKIM alignment alone, which makes a valid DKIM record a resilient second line of authentication - especially for forwarded mail, where SPF often breaks. Keep all three healthy: AutoSPF maintains the SPF side automatically, and our DKIM guide covers the rest.

DKIM is just one piece of the puzzle

AutoSPF handles SPF flattening so your DKIM and DMARC alignment stays intact. Start your free trial today.

Rated 5/5 on G2 · Trusted since 2018

What Our Customers Say

"AutoSPF Flattens SPF Records Seamlessly & Keeps Changes Logged - I am quite pleased with the product"

It does what it promises to do, and does it very well. I appreciate that it keeps a log of changes made, which prevents many mistakes. A client's SPF record would have way too many lookups, but AutoSPF makes that problem go away. The length of the SPF record is typically not the issue; it's the amount of lookups in the record that are. AutoSPF "flattens" the record, automatically expanding the defined lookups to IP addresses or ranges. And it auto-updates the record when the un-flattened lookups change.
PJ

Peter J.

President · Small-Business (50 or fewer emp.)

"Helped us go beyond capacity"

AutoSPF did exactly as described, it helped us get past our 10 lookup limit. Afterwards, we hit another limit regarding overall capacity and when contacted, they quickly provided us with a new solution to eliminate capacity issues entirely going forward, so now we can add as many SPF records as needed. They also provided us with a personalized support video explaining their new method in its entirety using our instance as the example.
VU

Verified User

Financial Services · Mid-Market (51-1000 emp.)