Skip to content
NewSee how
New

Email authentication: SPF, DKIM, and DMARC

Verify your sending domain's SPF, DKIM, and DMARC records right from the connector page, with one-click DNS setup for Cloudflare domains.

Email authentication is one of the most consequential, least visible parts of running cold outreach. SPF, DKIM, and DMARC records tell receiving mail servers that your emails are genuinely from you — not a spammer spoofing your domain. Without them, even well-written emails are more likely to land in spam or get rejected outright. Now you can check and fix all three directly from inside FirstSales, without leaving the app to dig through your DNS registrar.

Authenticate your sending domain

Each email connector now checks your SPF, DKIM, and DMARC records and shows you exactly what to add when something is missing.

What each record does

  • SPF (Sender Policy Framework) declares which servers are authorized to send email from your domain. Without it, receiving servers have no way to verify your messages are legitimate and are more likely to treat them with suspicion.
  • DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every outgoing email. It proves the message wasn't altered in transit and that it genuinely originated from your domain — a signal mailbox providers use when deciding where to deliver.
  • DMARC builds on SPF and DKIM by telling receiving servers what to do with mail that fails authentication checks, and provides reporting on how your domain is being used across the internet. It also blocks domain spoofing more effectively than either record alone.

All three together form the baseline for strong deliverability and for protecting your domain against misuse.

How to use it

  1. Open Connectors and click any email connector.
  2. The Email Authentication section shows pass/fail for SPF, DKIM, and DMARC.
  3. Click Set Up DNS Records for copy-paste instructions — or one-click publishing if your domain is on Cloudflare.
  4. If your email provider doesn't sign outgoing mail with DKIM, FirstSales can manage a DKIM key for you.

If a sending domain ever loses authentication — after a DNS change or a provider switch — you'll get an alert naming the affected domain so you can fix it fast.

Why it matters for inbox placement

Major mailbox providers — Gmail, Outlook, and others — have tightened their requirements around authentication. Domains without proper SPF, DKIM, and DMARC records face higher scrutiny. Getting all three in place before your first send is one of the highest-leverage steps toward consistent inbox placement.

If you haven't checked your connector's authentication status yet, open Connectors, click your sending account, and look at the Email Authentication section. The check runs instantly and tells you exactly what's missing. For most setups, adding the missing records takes under ten minutes — and the impact on deliverability compounds with every send after that.

All updates

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.