How to Verify Your Email Domain in Apollo.io?

Your emails are only as good as the inbox they land in. If you're sending cold outreach through Apollo.io without verifying your email domain, there's a real chance your carefully written messages are hitting spam folders before anyone reads them. Domain verification is the unglamorous backbone of successful email outreach — and most people skip it until something goes wrong.

Don't skip it.

What Is Email Domain Verification in Apollo.io?

Domain verification means proving to email providers like Gmail, Outlook, and Yahoo that you own the domain you're sending from, and that you've authorized Apollo.io to send on your behalf.

It involves configuring three DNS records:

• SPF (Sender Policy Framework) — tells receiving servers which IP addresses are allowed to send email on behalf of your domain
• DKIM (DomainKeys Identified Mail) — adds a cryptographic signature to your emails that proves they haven't been tampered with
• DMARC (Domain-based Message Authentication, Reporting & Conformance) — tells receiving servers what to do if SPF or DKIM checks fail (quarantine, reject, or allow)

Without these records, email providers treat your outreach as suspicious. With them, your emails are authenticated, trusted, and far more likely to reach the inbox.

Why This Step Is Non-Negotiable for Cold Outreach

Here's something most sales guides don't tell you: even if your email copy is perfect, your targeting is sharp, and your sequences are dialed in — none of it matters if your domain isn't authenticated.

Studies consistently show that properly authenticated domains see:

• 10–20% higher open rates vs. unauthenticated senders
• Significantly lower spam complaint rates
• Better long-term domain reputation scores

And if you're using Notion to track your outreach playbooks, content calendars, or campaign SOPs, pair it with a verified domain setup and you'll have a genuinely professional outbound operation.

Before You Start: What You'll Need

• Access to your domain registrar or DNS provider (GoDaddy, Cloudflare, Namecheap, Google Domains, etc.)
• Admin access to your Apollo.io account
• Your connected email account (Gmail or Outlook already linked to Apollo)
• About 20–30 minutes for setup, plus up to 48 hours for DNS propagation

Step-by-Step: How to Verify Your Email Domain in Apollo.io

Step 1 — Go to Email Settings in Apollo

Log into Apollo.io. Click your profile icon in the top-right and go to Settings. In the left sidebar, navigate to Mailboxes (sometimes listed under Email Settings depending on your plan).

Find the email account you've connected and click on it to open its settings.

Step 2 — Check Your Current Authentication Status

Apollo will show you the current status of your SPF, DKIM, and DMARC records. You'll typically see a red or yellow status if anything is missing or misconfigured.

This screen is your diagnostic dashboard. Note which records need attention.

Step 3 — Set Up Your SPF Record

Your SPF record tells the world which servers can send email on your domain's behalf.

To add or update your SPF record:

1. Log into your DNS provider
2. Go to your domain's DNS settings
3. Look for an existing TXT record starting with v=spf1
4. If one exists, add Apollo's sending servers to it — don't create a second SPF record (you can only have one)
5. If none exists, create a new TXT record

Apollo's SPF include value is typically:
include:spf.mandrillapp.com or as specified in your Apollo account — always check Apollo's own setup guide for the current value, as it can update.

A complete SPF record looks something like:
v=spf1 include:_spf.google.com include:spf.apollo.io ~all

Step 4 — Set Up Your DKIM Record

DKIM adds a digital signature to your outgoing emails. Apollo generates a unique DKIM key for your account.

To find your DKIM key in Apollo:

• Inside your Mailbox settings, look for the DKIM section
• Apollo will display a CNAME or TXT record with a specific selector and value
• Copy both the name (selector) and the value exactly

To add it to your DNS:

1. Go to your DNS provider
2. Create a new TXT record (or CNAME, depending on Apollo's instruction)
3. Paste the selector as the record name and the value as the record content
4. Save the record

Step 5 — Set Up Your DMARC Record

DMARC is the policy layer. It tells receiving servers what to do if your SPF or DKIM checks fail.

For a basic, safe setup, add this TXT record to your DNS:

• Name: _dmarc
• Value: v=DMARC1; p=none; rua=mailto:your@email.com

Starting with p=none means you're in monitoring mode — nothing gets rejected yet. Once you're confident everything is working, you can move to p=quarantine or p=reject for stronger enforcement.

Step 6 — Wait for DNS Propagation

DNS changes don't apply instantly. They can take anywhere from a few minutes to 48 hours to propagate globally.

During this time:

• Don't panic if Apollo still shows red status
• Use a free tool like MXToolbox or Google's Admin Toolbox to check propagation progress
• Come back to Apollo's mailbox settings and hit refresh after a few hours

Step 7 — Confirm Verification in Apollo

Once your DNS has propagated, return to Apollo's mailbox settings. Your SPF, DKIM, and DMARC indicators should now show green.

If any remain red, double-check that:

• You didn't accidentally create duplicate records
• The values were copied exactly (no extra spaces)
• You saved the records in your DNS provider correctly

Common Domain Verification Mistakes

Creating two SPF records:

DNS only allows one SPF record per domain. If you create a second one, email providers ignore both. Merge everything into a single v=spf1 line.

Using the wrong record type:

DKIM sometimes needs a CNAME, not a TXT record, depending on Apollo's configuration. Read the setup screen carefully.

Not verifying the sending subdomain:

If you're sending from a subdomain (like outreach.yourcompany.com), you need to set up DNS records for that subdomain specifically, not just your root domain.

Expecting instant results:

DNS propagation takes time. Many people check after five minutes, see it's still red, and assume something went wrong. Give it time.

Key Takeaways

• Domain verification requires setting up SPF, DKIM, and DMARC records in your DNS
• Apollo shows your current authentication status inside Mailbox settings
• Only one SPF record is allowed per domain — merge, don't duplicate
• DMARC should start with p=none (monitoring mode) and tighten over time
• DNS propagation can take up to 48 hours — be patient

FAQs

Do I need to verify my domain if I'm using Gmail?

Yes. Even with Gmail, if you're sending from a custom domain through Google Workspace, you still need SPF, DKIM, and DMARC configured on that domain.

What happens if I don't verify my domain?

Your emails are more likely to land in spam. Your domain reputation can be damaged over time, especially if recipients mark your emails as junk. Recovery is slow and painful.

Can I send cold emails in Apollo without domain verification?

Technically yes, but you shouldn't. Unverified domains have poor deliverability. You're essentially paying for sequences that never get seen.

What is a DMARC policy and which should I use?

Start with p=none (monitor only). Once you've confirmed SPF and DKIM are working correctly, move to p=quarantine to send suspicious mail to spam, then p=reject to block it outright.

How do I check if my domain is verified in Apollo?

Go to Settings → Mailboxes → click your connected email. Apollo displays a live status indicator for SPF, DKIM, and DMARC.

Final Thoughts

Domain verification isn't glamorous, but it's the difference between a cold email campaign that works and one that silently fails. Get your SPF, DKIM, and DMARC records set up before you send a single sequence. It's a one-time investment that pays dividends on every email you ever send.