How to Set Up Apollo.io Email With SPF, DKIM and DMARC

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Set Up Apollo.io Email With SPF, DKIM and DMARC.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Set Up Apollo.io Email With SPF, DKIM and DMARC.

To set up Apollo.io email with a verified domain, link a Google Workspace or Microsoft 365 mailbox in Apollo under Settings > Outbound > Domains & Mailboxes, then publish SPF, DKIM and DMARC records for that mailbox's domain at your DNS provider, and confirm all three read Good under Sequences > Diagnostics. Warm the mailbox for at least two weeks, test-send to colleagues, then start at 50 emails a day.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

Apollo doesn't send email from its own servers; its help pages say your linked mailbox sends everything. So authentication is about your domain, and so is the damage when it goes wrong. A domain that sends unauthenticated cold email can end up in spam for everyone, including the clients and candidates who were expecting to hear from you. That is why the records go in before the first sequence, not after the first bad week.

Should you send Apollo emails from your main domain or a second one?

Use a second, similar domain for sequenced outreach at 50 or more emails a day, and keep your main domain for light, personal sending. The first decision changes which domain every later step applies to. The illustration throughout is a six-consultant recruitment agency where two consultants will use Apollo for business development: emailing hiring managers at companies that are recruiting.

Send fromSuitsRisk
Your main domainUnder about 30 personal, researched emails a day per consultantSpam complaints hit the domain your clients, candidates and invoices use
A second, similar domainSequenced outreach at 50 or more a day, several mailboxesExtra mailboxes to pay for, and recipients may not recognise the name

Microsoft's guidance for Microsoft 365 recommends a subdomain for email services you don't directly control, so problems there don't affect your employees' main-domain mail, and Apollo offers lookalike domains for the same reason. If you take this route, choose a name that obviously belongs to you. Apollo's own example is that heyapollo.io is a fair alternative to apollo.io while a swapped-character version like heyapo11o.io can look suspicious. The agency chose a second domain: its main domain carries candidate and payroll emails it cannot afford to have filtered.

Apollo can also sell you the domain and mailboxes directly, under Settings > Outbound > Domains & Mailboxes (Domains first, then Add email & domain > Get a new domain), and says it handles authentication for domains bought that way. You still pick an address for DMARC reports, and purchases are non-refundable. The rest of this tutorial assumes you're using a domain and mailbox you set up yourself, which is where the authentication steps matter.

How do you link a mailbox to Apollo?

To link a mailbox to Apollo, open its Domains & Mailboxes settings and sign in to the Gmail or Outlook account you want to send from; each person links their own mailbox.

  1. In Apollo, go to Settings > Outbound > Domains & Mailboxes, click Mailboxes only, then Add email & domain > Link a mailbox I already have.
  2. Choose Google or Outlook, agree to the terms, click Link mailbox and sign in to the account you want to send from. Each person connects their own mailbox; Apollo says permissions apply only to the person who authorises the connection.
  3. For other providers choose Other, then your provider or Custom IMAP settings (email address, password, IMAP host, port and SMTP host).

Apollo says Gmail is its preferred provider, and that it doesn't support Google groups: link an individual mailbox. Plan limits apply here. The Free and Basic plans allow one mailbox per user; Professional allows unlimited Google and Microsoft mailboxes plus five custom IMAP or SMTP mailboxes per user. On price, Apollo lists Basic at $49 per seat a month billed annually and Professional at $79, and its email warm-up and deliverability tools start at Basic. For the agency, two Basic seats is $98 a month billed annually. The full plan comparison is in Apollo's plans and credits compared.

What is SPF and where does it go for Apollo?

SPF (Sender Policy Framework) is a TXT record in your domain's DNS that lists which servers may send email for it, and Apollo wants it on the domain your linked mailbox sends from. If you send as [first name]@youragency.com, the record belongs on youragency.com, not on a tracking subdomain or your website's hosting.

The values come from your email provider, not from Apollo:

Google Workspace only:   v=spf1 include:_spf.google.com ~all
Microsoft 365 only:      v=spf1 include:spf.protection.outlook.com -all

Host / name:  @  (the domain itself)
Type:         TXT

Google recommends ending with ~all; Microsoft recommends -all once DKIM and DMARC are in place. Either passes. Three rules matter more than that choice:

  • One SPF record per domain. Microsoft's documentation is explicit that more than one SPF TXT record on the same domain makes SPF fail with a permanent error. If a record already exists, add to it; never add a second.
  • Every sender goes in that one record. If your website's contact form, your accounts software or a newsletter tool sends as your domain, each needs its include: entry. Google's page allows up to 10 include: tags.
  • Stay under 10 DNS lookups. Microsoft notes each include: costs at least one lookup and nested ones cost more; past 10, SPF fails outright. Free online SPF checkers count them for you.

Google says SPF can take up to 48 hours to start working. A before-and-after from an illustrative setup shows the commonest mistake:

Before (two records: SPF fails for both)
TXT  @  v=spf1 include:_spf.google.com ~all
TXT  @  v=spf1 include:servers.newsletter-tool.example ~all

After (one merged record)
TXT  @  v=spf1 include:_spf.google.com include:servers.newsletter-tool.example ~all

What is DKIM and how do you add it?

DKIM (DomainKeys Identified Mail) signs each outgoing email with a private key, and receivers check it against a public key published in your DNS. It is the record that proves a message wasn't altered and really came from your mailbox provider on your behalf.

Google Workspace: in the Admin console go to Apps > Google Workspace > Gmail > Authenticate email. Google says to wait 24 to 72 hours after Gmail is turned on before generating a key, choose 2048-bit if your DNS provider supports it, and keep the default prefix "google". Click Generate New Record, then add a TXT record at the host google._domainkey with the value shown (it starts v=DKIM1; k=rsa; p=). Google says DKIM can take up to 48 hours to start working; then click Start authentication, and the status changes to "Authenticating email with DKIM".

Microsoft 365: in the Defender portal go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings, open the DKIM tab and select your domain. Microsoft uses two CNAME records, at selector1._domainkey and selector2._domainkey, whose exact values the portal shows for your domain. Add both, wait, then turn on "Sign messages for this domain with DKIM signatures". A status of CnameMissing means the records aren't visible yet.

Google's sender guidelines require DKIM keys of at least 1,024 bits and recommend 2,048, which is the other reason to pick 2048-bit when you can.

Which DMARC policy should you start with?

Start DMARC with p=none, which reports failures and blocks nothing, and move to p=quarantine only after a few weeks of reports show just your own services. DMARC tells receiving servers what to do when a message fails SPF and DKIM, and sends you reports about who is sending as your domain. Google's advice is to allow 48 hours after setting up SPF and DKIM before adding DMARC, and to start with a policy that takes no action:

Host / name:  _dmarc
Type:         TXT
Value:        v=DMARC1; p=none; rua=mailto:dmarc-reports@youragency.com

p=none means "report, don't block". The rua address receives daily aggregate reports from receiving providers; Google and Apollo both suggest a dedicated mailbox or a monitoring service rather than a personal inbox, because the reports pile up. After a few weeks of reports showing only your own services, move to p=quarantine, and later to p=reject if you're confident. Google's page describes a pct tag for applying the stricter policy to a percentage of failing mail first.

For context on why this is no longer optional: Google's sender guidelines, in force since February 2024, require every sender to Gmail to have SPF or DKIM, and anyone sending 5,000 or more messages a day to have SPF, DKIM and DMARC, aligned domains and one-click unsubscribe for marketing mail. A two-consultant agency is nowhere near 5,000 a day, but receiving servers judge small senders by the same signals.

How do you confirm in Apollo that authentication works?

Go to Sequences > Diagnostics: under Domain setup, Apollo shows SPF, DKIM and DMARC for each mailbox's domain as Good or Fix. Click the refresh icon if nothing appears. For a Fix, Apollo can update the records itself for some DNS providers once you grant access, or you can choose Go to manual setup and copy the records yourself. If someone else manages your DNS, Forward instructions to a colleague sends them a link that works for 24 hours.

One trap Apollo's own page flags: the company you registered the domain with may not be the one hosting its DNS. Check which provider runs the domain's nameservers before editing anything; records added in the wrong place do nothing.

Then set up a custom tracking subdomain under Settings > Outbound > Tracking, Create Subdomain. Apollo uses it for the links and tracking pixels in your emails, recommends one per sending domain, and suggests short names such as track or go. With automatic addition it creates the CNAME record for you; check the subdomain 24 hours later for a healthy status. Tracking is optional: if you don't need open and click figures, you can leave it off and skip this step.

If you want help fitting outreach like this into how your business actually runs, I offer one-to-one AI consultations for small businesses.

How long should you warm up an Apollo mailbox?

Warm up an Apollo mailbox for at least two weeks before the first sequence. Apollo's warm-up connects your mailbox to third-party providers that exchange system-generated test emails with a private network of inboxes, opening and replying to build your sender reputation. It doesn't use your sequences or templates. To start it, go to Settings > Outbound > Domains & Mailboxes, click Mailboxes only, and toggle Start warm up beside the mailbox, then sign in with Google (recommended) or an app password. Microsoft 365 mailboxes need SMTP AUTH enabled, or warm-up can't run.

The settings, filled in with Apollo's recommendations:

SettingApollo's recommendationLimit
Warm-up typeProgressive (volume rises gradually)Flat and Randomized also offered
End dateAt least two weeks out
Minimum emails a day10
Maximum emails a day40No more than 50
Reply rate a day30%No more than 45%

Warm-up traffic doesn't count against your Apollo sending limit. Expect test messages in the mailbox; Apollo explains how to filter them out of view. For a brand-new domain, Apollo's advice is to give the domain and mailbox time to build reputation before any cold outreach, which is what the two weeks are for.

How do you test that Apollo authentication works?

Test by sending three plain emails through Apollo, to a Google, an Outlook and another provider's address, then reading the Authentication-Results header for three passes. Google's DKIM guide says not to test by emailing yourself. In Gmail, open the message, click More next to Reply, and choose Show original. The header looks something like this (illustrative and shortened):

Authentication-Results: ...
   dkim=pass header.i=@youragency.com
   spf=pass (... domain of [first name]@youragency.com designates ... as permitted sender)
   dmarc=pass (p=NONE ...) header.from=youragency.com

All three should say pass, and the domain after header.i and header.from should be your sending domain. Ask the Outlook recipient whether the email landed in the inbox or junk. A pass with a junk placement points at content or reputation, not authentication; a fail points back at Steps 2 to 4.

If a test lands in junk despite three passes, work through this before blaming the records: send a plain version with no images, attachments or links and see whether it lands differently; make sure the From name is a person, not the agency's name in capitals; check that warm-up is still running in Email setup and health; and give it another week of warm-up before testing again. Change one thing at a time, or you won't know which change helped.

How many emails a day should a new Apollo mailbox send?

A new Apollo mailbox should start at 50 emails a day and 6 an hour, the default limits Apollo's help recommends.

Apollo's authentication page suggests starting at 50 emails a day and 6 an hour. Its sending-limits page recommends 50 emails a day, 6 an hour and a 600-second (10-minute) delay between emails as the default limits per mailbox. Set them in Settings > Outbound > Domains & Mailboxes: click Mailboxes only, then the ellipsis (…) in the mailbox's Actions column > Configure mailbox > Sending limits. Apollo advises increasing daily volume gradually only once you consistently see at least a 5% reply rate and a strong domain reputation; to grow, it advises adding mailboxes rather than raising one mailbox's limit.

Two rules about how Apollo counts change the arithmetic. The Sent vs Limit counter covers a rolling 24 hours, not a calendar day, and includes sequence steps, manual emails, one-off emails and follow-ups. Emails over the limit aren't dropped; they stay scheduled until capacity returns. And mail you send from the same mailbox outside Apollo isn't counted, so if consultants also use these mailboxes for day-to-day email, set Apollo's limit lower.

The agency's illustrative timeline and numbers:

WhenWhat happened
Day 0Second domain registered; two Google Workspace mailboxes created
Day 1SPF published
Day 2DKIM key generated (after Google's 24-72 hour wait), TXT record added
Day 4DKIM authenticating; DMARC p=none added; mailboxes linked to Apollo; Diagnostics all Good
Day 4Tracking subdomain created; warm-up started (Progressive, 10 to 40 a day, 30% replies, 14 days)
Day 18Test sends: all pass, inbox at Gmail and Outlook
Day 19Limits set to 50 a day, 6 an hour, 600 seconds apart; first sequence starts
Week 6Reply rate 6.5% over three weeks; limit raised to 60 a day per mailbox

The quick sum that surprises people: the limit covers follow-ups, so it isn't 50 new prospects a day. With a three-email sequence, each prospect eventually takes three of the mailbox's daily slots. Once the sequence is running at full stretch, two mailboxes at 50 a day carry about 33 new prospects a day between them (100 sends divided by 3), or around 165 a week over five days. That is plenty for a recruitment agency writing to hiring managers it has researched; if it isn't, the answer is another mailbox, not a higher limit. Before loading prospects, importing, enriching and scoring your first 500 leads covers the list side.

Two more things every Apollo email should carry. Apollo recommends an unsubscribe link in your signature or templates, because people who can opt out are less likely to report spam. And the legal side of emailing people who never asked to hear from you varies by recipient, which whether Apollo.io is safe and legal to use works through.

If your prospect lists and sending logs live in spreadsheets, try The Complete Excel Course with AI Integration on Coding Liquids.

What Apollo setup mistakes hurt deliverability?

Four setup mistakes hurt Apollo deliverability: a second SPF record, records added at the registrar instead of the DNS host, DMARC set straight to reject, and starting sequences on day one.

A second SPF record

Someone adding the newsletter tool pasted a new SPF record instead of editing the existing one. The symptoms: Apollo's Diagnostics flipped SPF to Fix, and the Show original header read spf=permerror. The fix was merging both include: entries into one record, as in the Step 2 example.

Records added at the registrar, not the DNS host

The domain was registered with one company but its nameservers pointed to the website host. Every record added at the registrar was ignored, and Diagnostics kept saying Fix for two days. Check the nameservers first, then edit records where they point.

DMARC set straight to reject

On the main domain, a p=reject policy went live on day one. The agency's job-board alerts and its timesheet system both sent as the main domain without being in SPF or signed with DKIM, so their emails started failing DMARC and disappearing. Starting at p=none and reading two or three weeks of reports would have listed both services before anything was blocked.

Starting sequences on day one

The temptation is to authenticate in the morning and send in the afternoon. A new mailbox sending 50 cold emails on its first day looks exactly like a spammer to receiving servers, whatever its records say. Google's own guidance for senders is to increase volume slowly and avoid sudden spikes. The two weeks of warm-up are the cheapest part of the whole setup; if you're weighing whether outbound is worth it at all for your firm, AI for recruitment business development looks at the wider approach to winning clients.

Apollo email setup: what owners ask next

Does Apollo send my emails from its own servers?

No. Apollo's help pages say it doesn't send emails on your behalf: sequence emails go out through the mailbox you link, such as Google Workspace or Microsoft 365. That is why authentication has to be set up on your mailbox's own domain, and why any damage to sender reputation lands on that domain, not on Apollo.

Can I skip all this by buying a domain and mailbox inside Apollo?

Partly. Apollo can register a new domain and create mailboxes, and says it handles the domain authentication for you, asking for an address to receive DMARC reports along with your registration details. You still need warm-up and sensible limits, Apollo advises giving the new domain time to build reputation before cold outreach, and purchases are non-refundable.

Why isn't Apollo sending as many emails as my limit allows?

Usually because another limit is lower. Apollo uses the lower of its ramp-up limit and your configured limit, counts a rolling 24 hours rather than resetting at midnight, and your mailbox provider applies its own unpublished limits. Emails over the limit stay scheduled and go out as capacity returns.

Should the DMARC reports go to my own inbox?

No. Aggregate reports arrive daily from each receiving provider and can be numerous once DMARC is on. Google and Apollo both suggest a dedicated mailbox or a monitoring service. A shared address such as a reports mailbox, checked weekly for unknown senders and failures, is enough for a small business.

How long should I warm up an Apollo mailbox before sending?

At least two weeks. Apollo's recommended warm-up settings use a progressive ramp with an end date at least two weeks out, and its advice for a brand-new domain is to give it time to build reputation before any cold outreach. Warm-up traffic doesn't count against your Apollo sending limit.

Further reads

Sources: Apollo knowledge base (Diagnose and Fix Domain Authentication on Apollo, Link Your Mailbox to Apollo, Use Email Warmup to Improve Deliverability, Configure Email Sending Limits, Set Up a Custom Tracking Subdomain, Generate a Domain and Mailbox to Reach Prospects); Apollo pricing page; Google Workspace help on SPF, DKIM, DMARC and email sender guidelines; Gmail help on full headers; Microsoft Learn on SPF and DKIM for Microsoft 365. Checked 18 Nov 2026.

Want a second pair of eyes on your setup?

Bring the process you're trying to fix. On a 1:1 call we'll work out which AI tools should handle it, which parts stay manual, and how to roll it out without disrupting the team.

Book a 1:1 call with me