Skip to content
OutboundQA

Free tool

Free DKIM record checker

Look up a DKIM selector for a sending domain and see whether the public key exists before a cold email launch.

This checks DKIM selector for one domain. For a real launch verdict, run every domain, inbox, and tracking domain through the full QA pass.

Runs live in your browser via public DNS. Nothing is stored.

How to read the result

A DKIM record usually lives at selector._domainkey.yourdomain.com. A healthy selector returns one TXT record with a public key in p=. If the selector is unknown, test the selector from your actual sending platform before treating the domain as ready.

DKIM is one of the authentication checks OutboundQA runs across every workspace domain and inbox. A single passing selector is useful, but a launch verdict needs the selector matched to the tool that will send the campaign.

What this check does not catch

A passing DKIM selector lookup is useful, but it is not launch signoff. Cold email campaigns still fail when adjacent records, tracking domains, or inbox-level settings are broken.

SPF lookup limits
DMARC alignment
MX readiness
tracking-domain SSL
blacklist status
inbox-level sending setup

Setup guides for this check

Read the setup notes behind this result, then verify the neighboring records before launch.

Need to check a full outbound workspace?

OutboundQA checks every domain, inbox, and tracking domain in the workspace, then gives you a shareable report with a Ready, Needs Fix, or Do Not Launch verdict.

Questions

A selector is the DNS label your mail provider uses to find the right DKIM key. The lookup happens at selector._domainkey.yourdomain. Common selectors include google, selector1, selector2, s1, and s2, but every provider can choose its own value.

DKIM signs outbound mail so receivers can verify the message was authorized by the domain. Without DKIM, DMARC alignment is weaker and Google or Microsoft may treat the campaign as higher risk.

Check your sending platform's domain authentication screen. Google Workspace commonly uses google, Microsoft often uses selector1 and selector2, and many outbound tools use s1 or s2. Unknown selector is different from failed DKIM, so test the selector your platform actually sends with.