DKIM: A Plain-English Guide for Recruitment Agencies
TL;DR
- DKIM is a digital signature on every email you send. It proves the message came from your domain and wasn’t changed on the way.
- Your agency doesn’t send from one place. Outlook, your ATS, your outreach platform, your newsletter tool and your website forms each need their own DKIM, signed as your domain.
- A tool can pass DKIM and still fail DMARC if it signs as itself instead of you. This is the gap we find most often.
- You can check any email’s DKIM result in Gmail in under two minutes. Steps below.
When a candidate’s inbox decides whether your email is genuine, DKIM is one of the first things it checks. If the signature is missing or broken, your job alert, spec CV or client update arrives under suspicion. Gmail and Outlook are now strict enough that suspicion usually means junk.
When we audited 490 UK and US recruitment agencies, nearly half had DKIM missing. Most had no idea, because the emails still sent. They just stopped landing.
This guide covers what DKIM is, where agencies usually get it wrong, and how to check yours today.
What is DKIM?
DKIM (DomainKeys Identified Mail) is an email authentication method that adds a digital signature to every message you send. The receiving server checks that signature against a public key published in your domain’s DNS. If they match, the email is proven to come from your domain and to be unchanged since it left.
Think of it as the hologram on a banknote. Anyone can print something that looks right. Only the genuine article carries a mark the receiver can verify.
How DKIM works
- Your sending system holds a private key. It never leaves that system.
- When an email goes out, the system creates a signature from key headers (From, Subject, Date) and a fingerprint of the body, and adds it to the message as a DKIM-Signature header.
- That header names the signing domain (d=) and the selector (s=), a label saying which key was used.
- The receiving server looks up the public key at selector._domainkey.youragency.co.uk and checks the signature.
- The result is pass, fail (the signature doesn’t verify, usually because the message was altered or the key is wrong) or none (no signature at all).
The candidate never sees any of this. They see the outcome: inbox, junk, or a warning banner.
What a DKIM record looks like
DKIM records live in your DNS in one of two forms.
A TXT record holding the public key itself, as Google Workspace uses:
Host: google._domainkey.youragency.co.uk
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOC...
A CNAME record pointing to a key the provider hosts and rotates for you, as Bullhorn uses:
Host: bh._domainkey.youragency.co.uk
Points to: bh._domainkey.bullhornmail.com
The “google” and “bh” parts are selectors. Each tool has its own, which is why one domain can hold several DKIM records without them clashing. CNAMEs are usually the better option for third-party tools, because the provider can rotate keys without anyone touching your DNS. Where you have the choice, use 2048-bit keys.
Every tool you send from needs its own DKIM
This is where recruitment agencies get caught. A typical agency sends as its own domain from five or more systems:
| What sends it | Typical examples | DKIM setup |
|---|---|---|
| Consultant mailboxes | Microsoft 365, Google Workspace | M365: two CNAMEs, then signing switched on in Defender. Google: one TXT key. |
| ATS / CRM | Bullhorn, Vincere, JobAdder, Firefish, TrackerRMS | Record supplied by the provider, TXT or CNAME depending on platform |
| Outreach platform | Sourcewhale, Instantly | None required, as they send from your M365 or Google mailboxes! |
| Automation tools | Bullhorn Automation, Spott Marketing | Record supplied by the provider, set in the platform’s domain settings |
| Newsletters and marketing | Mailchimp, HubSpot and similar | Usually one or two CNAMEs per domain |
| Website forms and job alerts | Your website platform, job board integrations | Often not signed as your domain at all |
Every one needs its own record. And here’s the trap: each platform’s setup screen only checks its own. Sourcewhale will show a green tick when Sourcewhale’s DKIM is right. It has no idea whether Bullhorn or your newsletter tool is signing correctly. Five green ticks in five dashboards is not the same as a domain that authenticates cleanly. We cover this in more depth in why your outreach platform says everything’s fine.
Every new tool, ATS migration or marketing platform switch means revisiting DKIM. We regularly find agencies that changed ATS years ago, still have the old provider’s records in DNS, and have nothing set up for the new one.
DKIM pass isn’t enough: alignment
DKIM proves that a domain signed the message. It doesn’t prove it was your domain. Plenty of tools sign as themselves by default, so the email passes DKIM as d=sendingplatform.com while your agency’s address sits in the From line.
DMARC won’t accept that. It requires alignment: the domain in the DKIM signature must match the domain in the From address (or share the same root domain). A tool that signs as itself passes DKIM and still contributes nothing to your DMARC result. If SPF doesn’t align either, the message fails DMARC, and with a quarantine or reject policy in place it goes to junk or never arrives.
So when a platform offers “custom domain”, “authenticated domain” or “branded sending” setup, complete it. The basic setup gets mail out the door. The domain setup gets it trusted.
What DKIM doesn’t do
- It doesn’t stop spoofing on its own. A spoofer can sign with their own domain and pass DKIM. DMARC, enforcing alignment, is what stops someone sending as your domain.
- It doesn’t reject email by itself. A failed signature is evidence. What happens next depends on your DMARC policy and the receiver’s filters.
- It doesn’t authenticate the person. If a consultant’s mailbox is compromised, the attacker’s emails get signed perfectly.
- It doesn’t make your email wanted. Authentication gets you through the door. Engagement, data quality and sending volume decide whether you stay.
Why DKIM fails in recruitment agencies
- The tool was never authenticated. Someone connected a newsletter tool three years ago and nobody published its DKIM.
- Records published, signing never switched on. Common in Microsoft 365, where adding the CNAMEs is only half the job. See how to set up DKIM in Microsoft 365.
- ATS migration. Old records left in, new ones missed.
- Something edits the email after it’s signed. Some security gateways, disclaimer tools and list services add text or rewrite links after signing, which breaks the signature.
- A clipped key. Some DNS panels truncate or mangle long TXT values.
- DNS moved hosts. Records not copied across when the domain or DNS moved provider.
How to check your DKIM in two minutes
- Send an email from the system you want to test (your mailbox, a test job alert from your ATS, a test campaign) to a Gmail address.
- Open it in Gmail, click the three dots, and choose Show original.
- Find the DKIM line. You want PASS with domain youragency.co.uk. A pass with someone else’s domain means it isn’t aligned. FAIL, or no DKIM line at all, means it isn’t working.
- Repeat for every tool that sends as your domain.
That tests one email from one tool. To see every source sending as your domain, including the ones nobody remembers setting up, you need DMARC reporting. Quinset Powermail turns those reports into DKIM results by sending source, so a broken ATS signature shows up as a line item rather than a mystery drop in replies. For a quick first look, run a free domain health check.
What this means for recruiters
- Unsigned or misaligned email is filtered first. Google, Yahoo and Microsoft all now require authentication from high-volume senders, and an agency’s job alerts alone can push it into that bracket. More in Google’s new email rules.
- The cost is commercial. Candidates who miss the job alert apply through someone else. Clients who don’t see the shortlist assume you’ve gone quiet.
- The fix is small. Finding it is the work. DKIM is usually a record or two per tool. The hard part is knowing every system sending as your domain and confirming each one aligns.
- Nobody owns the whole picture. Your IT provider runs Microsoft 365, the ATS vendor owns their records, marketing set up the newsletter tool. Each sees their own piece. That gap is where email deliverability for recruitment agencies usually breaks down.
DKIM FAQs
What does DKIM stand for? DomainKeys Identified Mail. It’s an email authentication standard that signs outgoing messages so receivers can verify who sent them.
Do I need DKIM if I already have SPF? Yes. SPF often breaks when email is forwarded, while DKIM usually survives. Google, Yahoo and Microsoft also expect both from anyone sending at volume, which includes most agencies running job alerts or outreach. See what is SPF.
Can a domain have more than one DKIM record? Yes. Each sending tool uses its own selector, so you can have as many DKIM records as you have sending platforms.
What does dkim=none mean? The email wasn’t signed at all. Usually the tool was never authenticated for your domain, or signing was never switched on.
Why does my email pass DKIM but fail DMARC? The signature belongs to a different domain from the one in your From address. Complete the tool’s custom domain setup so it signs as your domain.
How often should DKIM keys be rotated? At least once a year is sensible practice. Providers using CNAME records rotate keys for you. Self-managed TXT keys need doing by hand.
Not sure which of your tools are signing correctly?
Most agencies we speak to have at least one sending system that’s unsigned or misaligned, and nobody knows which. Book a 30-minute call with Ben and we’ll check every system sending as your domain, tell you which ones are failing, and what to fix first.
Book a call with Ben and get your setup checked today.
Quinset is an email deliverability consultancy for recruitment agencies in the UK and US.




