Skip to content
NewSee how

Email authentication

Email authentication that sets up SPF, DKIM and DMARC for you.

Three DNS records decide whether inbox providers believe your email is really from you. FirstSales shows the exact records for each mailbox, writes them for you on Cloudflare, can manage your DKIM keys, and checks that every record is live before you send.

$1 for 3 days · Cancel anytime · No contract

The Connectors page in the FirstSales sample workspace, with connected email mailboxes, a calendar and a notification bot, each showing when it was last verified
  • 01

    Exact records for every mailbox, ready to copy

  • 02

    One-click setup when your domain is on Cloudflare

  • 03

    Managed DKIM with automatic key rotation

  • 04

    Included in every plan, from $29/mo

The problem

Without authentication, good email looks like a fake.

Inbox providers see a flood of forged email every day. If your domain cannot prove a message is really yours, your careful, personal outreach gets treated like the rest.

Spam or rejected

Mail with no SPF, DKIM or DMARC is easy for providers to distrust. It lands in spam, or it never arrives at all, and nothing tells you which.

DNS feels like a trap

Hosts, values, TXT, CNAME, selectors. One wrong character and the record silently fails. Most people copy a value from a blog post and hope.

The rules got stricter

Gmail and Yahoo now reject unauthenticated bulk mail outright. At higher volume, skipping authentication is no longer a risk you can take.

How it works

Copy, add, check. Then send.

Authentication lives on each mailbox's Technical tab. It tells you what to add, helps you add it, and confirms when it is live.

  1. 01

    Open the Technical tab

    On the Connectors page, open your sending mailbox and go to Technical. You see SPF, DKIM and DMARC, each with the exact record for your domain.

  2. 02

    Add the records

    Copy each record into your DNS host, or press Add to Cloudflare if your domain is there. The score bar shows how far along you are.

  3. 03

    Check they are live

    Press Check DNS Records. Each record shows pass or fail. When all three pass, you see All checks passed and you are ready to send.

Three records, three jobs

What each record tells the inbox.

SPF, DKIM and DMARC sound like one big technical chore. They are three short lines of text in your DNS, and each one answers a different question a mailbox provider asks about your email.

  • SPFSender Policy Framework

    Type
    TXT
    Host
    @
    Value
    v=spf1 include:_spf.mail.example ~all

    Declares which servers may send mail for your domain.

    Anyone can claim to send as you, so providers trust nothing that says it is from you.

  • DKIMDomainKeys Identified Mail

    Type
    CNAME
    Host
    fs1._domainkey
    Value
    fs1.dkim.mail.example

    Signs every outgoing email so it cannot be forged or changed on the way.

    Providers cannot tell your real email from a copy someone tampered with.

  • DMARCDomain-based Message Authentication

    Type
    TXT
    Host
    _dmarc
    Value
    v=DMARC1; p=none; rua=mailto:[email protected]

    Tells receivers what to do when SPF or DKIM fail.

    Each provider guesses what to do with failing mail, and guesses tend to go badly.

Sample values. Your real records are generated for your domain, and the DKIM selector is unique to you. Always copy them from your own Technical tab.

What you get

Authentication done right, without learning DNS.

Everything you need to prove your email is yours, in the same place you connect the mailbox.

  • Your exact records

    No generic values from a guide. Each mailbox shows the records generated for its own domain, with the host and value side by side.

  • One click on Cloudflare

    When your domain runs on Cloudflare, FirstSales can write the missing records for you. No copy and paste, and no typos.

  • DKIM that looks after itself

    For SMTP/IMAP and relay mailboxes, Managed DKIM creates the signing key and rotates it over time. You add one CNAME, once.

  • A score you can read

    A single bar per mailbox shows how much of its authentication is in place, from Not Secured to Fully Authenticated.

  • Live checks on demand

    Check DNS Records confirms each record from the outside, the way a mailbox provider sees it, and shows pass or fail per record.

  • Part of a full safety net

    Authentication works alongside warm-up, list cleaning and hourly health checks, so each layer protects the others.

From no recordsto fully authenticated

Four parts of authentication in FirstSales, and what each one does for you.

  1. The Technical tab

    Every record you need, on one screen

    Open any sending mailbox and go to Technical. SPF, DKIM and DMARC each get a row with its status and the exact record to add. Nothing to look up, nothing to guess.

    • Per-domain records. Generated for your domain, including your own DKIM selector.
    • Host and value side by side. The two fields every DNS host asks for, ready to copy.
    • Status per record. See at a glance which records are live and which are missing.
  2. Cloudflare one-click

    On Cloudflare? Let FirstSales add the records

    If your domain uses Cloudflare, the Technical tab says so and offers Add to Cloudflare. Paste a scoped token, review the list, and apply. Only missing records are added.

    • Scoped token. Zone, DNS, Edit on the one domain. Nothing broader is needed.
    • Never stored. The token is masked, used for one request and then dropped.
    • Only what is missing. The list shows exactly what it will create, so nothing you have is replaced.
  3. Managed DKIM

    Add one CNAME and forget key rotation

    For SMTP/IMAP and relay mailboxes, press Enable Managed DKIM. FirstSales creates the signing key and gives you one CNAME record. After that, it rotates the key over time with no more DNS changes.

    • Key created for you. No key files to generate or keep safe.
    • Automatic rotation. Keys change over time without you touching DNS again.
    • Google and Microsoft. These mailboxes manage DKIM themselves, so there is no button to press.
  4. Verify

    Confirm every record is live before you send

    Press Check DNS Records and each record shows pass or fail. DNS changes can take up to 48 hours to spread, so a fail right after adding a record usually just means wait, then Re-check.

    • Pass or fail per record. Know exactly which record still needs work.
    • All checks passed. One clear message when the full set is live.
    • Re-check any time. Run it again after DNS has had time to spread.
One score

See how far along you are, one record at a time.

Each mailbox gets an authentication score. SPF counts for 34 percent, DKIM and DMARC for 33 percent each, so the bar moves every time a record goes live.

Authentication score

SPF34%

DKIM33%

DMARC33%

  1. Not Secured

    No records pass yet

    Mail from this mailbox is likely to be filtered or rejected. Start with whichever record is easiest for you.

  2. Partially Protected

    One or two records pass

    Better, but partial authentication still gets filtered. Providers want the full set.

  3. Fully Authenticated

    All three records pass

    The score reaches 100 percent. This is the foundation every other part of deliverability builds on.

The check is advisory. It never blocks you from sending, but unauthenticated mail tends to land in spam, so treat it as required.

Plain guide

Email authentication, explained without jargon.

What SPF, DKIM and DMARC are, why they matter for cold email, and how to get them right the first time.

  1. 01

    What email authentication is

    Email was built without any way to prove who sent a message. Anyone can put any name in the From line. Email authentication fixes that with three small records in your domain's DNS. Together they let a receiving server check that a message really came from your domain, was not changed on the way, and should be trusted. Without them, a provider has to guess, and providers guess cautiously.

  2. 02

    SPF in one paragraph

    SPF, short for Sender Policy Framework, is a list of the servers allowed to send email for your domain. When a message arrives, the receiving server looks up that list and checks whether the sending server is on it. If it is not, the message looks like someone pretending to be you. You only get one SPF record per domain, so when you add a new sending service you add it to the same record instead of creating a second one.

  3. 03

    DKIM in one paragraph

    DKIM, short for DomainKeys Identified Mail, adds a digital signature to every message you send. The matching public key lives in your DNS. The receiving server uses it to check the signature. If the signature holds, the message came from you and was not changed in transit. DKIM keys should be rotated from time to time, which is exactly the chore Managed DKIM takes off your plate.

  4. 04

    DMARC in one paragraph

    DMARC, short for Domain-based Message Authentication, ties SPF and DKIM together. It tells receiving servers what to do when a message fails those checks: let it through, send it to spam, or reject it. It can also ask for reports about mail sent as your domain. Many senders start with a gentle policy while they confirm everything passes, then tighten it once they are confident.

  5. 05

    Why cold email needs all three

    A cold email arrives from someone the reader has never heard of. That alone makes providers careful. Authentication is how you remove the first and easiest reason to filter you. Partial setups still get filtered, because providers want the full set. Large providers now require authentication from anyone sending in bulk, and Gmail and Yahoo reject unauthenticated bulk mail with error 550-5.7.26. Below that level it is still strongly recommended for every sender.

  6. 06

    Why your records must be your own

    Authentication records are not one size fits all. Your SPF lists your sending servers, and your DKIM selector and key are generated for your domain alone. Copying a value from someone else's guide is the most common reason a record fails. Always copy from your own Technical tab, and match each field exactly, without extra spaces or quotes unless your DNS host asks for them.

  7. 07

    Authentication is the floor, not the ceiling

    Passing SPF, DKIM and DMARC proves your email is yours. It does not prove anyone wants it. Inbox placement also depends on a warmed mailbox, a clean list, a steady sending pace and emails that people read and answer. Think of authentication as the foundation. Nothing else holds without it, and it is not enough by itself.

Any DNS host

Different labels, the same two fields.

Every record is a type, a host and a value. Each DNS host just names those fields its own way. Here is where to paste each part at the hosts people use most.

DNS hostCalls the hostCalls the valueWhere to add it
CloudflareNameContent

DNS → Records → Add record

Keep mail records DNS-only, the grey cloud. Proxying them breaks them. Or skip all of this with one-click.

GoDaddyNameValue

Domain → DNS → Manage Zones

Use @ for the root domain. Save, then give it time to spread.

NamecheapHostValue

Domain List → Manage → Advanced DNS

Use @ for the root domain. Records live under Advanced DNS.

AWS Route 53Record nameValue

Hosted zones → your zone → Create record

Wrap TXT values in quotes, the way Route 53 expects them.

Using a different DNS host? It still asks for the same type, host and value. Match the fields and save.

Before you send

An authentication checklist for every mailbox

Run through it each time you connect a mailbox or move a domain to a new DNS host.

  • SPF, DKIM and DMARC are all added, not just one or two
  • Every value was copied from your own Technical tab
  • There is only one SPF record on the domain
  • On Cloudflare, mail records are DNS-only, not proxied
  • Managed DKIM is on for SMTP/IMAP and relay mailboxes
  • Check DNS Records shows all three passing
  • You waited before re-checking a fresh record
  • The authentication score reads 100 percent
  • The mailbox is warming up before campaigns start
  • Your list is cleaned before the first send
“One of the biggest pains in cold email is making sure that you have your DNS setup correctly. Firstsales has created a system to make sure you have done this correctly.”
Mike OTrustpilot review · Trustpilot
Before and after

Setting up authentication, the old way and with FirstSales

The same three records, a very different afternoon.

On your own

Guides, guesswork and waiting.

  • Hunt for the right valuesCopied from a guide that was not for your domain.
  • Paste by handOne typo and the record quietly fails.
  • Manage DKIM keysGenerate them, store them, rotate them, forever.
  • No clear statusIs it live, still spreading or wrong? Hard to tell.
  • Learn every DNS hostEach one labels the fields differently.
  • Find out from bouncesThe first sign of trouble is mail that never arrives.
With FirstSales

Exact records, checked for you.

  • Your exact recordsGenerated for your domain, ready to copy.
  • One click on CloudflareMissing records written for you.
  • Managed DKIMOne CNAME, and rotation is automatic.
  • Pass or fail per recordCheck DNS Records shows exactly where you stand.
  • Same two fields everywhereHost and value, whatever your DNS host calls them.
  • Know before you sendA score per mailbox, before any campaign starts.
Why teams switch

Email authentication: FirstSales vs a typical tool

Many tools tell you to set up SPF, DKIM and DMARC and leave the rest to you. FirstSales walks each mailbox through it.

Email authentication in FirstSales and in a typical cold email tool
What you getTypical toolFirstSales
Records per mailboxVariesExact SPF, DKIM and DMARC shown
Cloudflare setupVariesOne click with a scoped token
DKIM keysVariesManaged, with automatic rotation
Live checkVariesPass or fail per record
ProgressVariesWeighted score per mailbox
Token handlingVariesMasked, used once, never stored
Existing recordsVariesOnly missing ones are added
PriceVariesFrom $29/mo, included
Start your $1 trial

Questions,answered plainly.

Can’t find yours? Write to us.

01What is email authentication?

It is three DNS records, SPF, DKIM and DMARC, that let inbox providers check your email really comes from your domain. FirstSales shows the exact records for each mailbox and checks that they are live.

02Where do I set it up in FirstSales?

On the Connectors page, open your sending mailbox and go to the Technical tab. It lists each record to add at your DNS host, then verifies them with Check DNS Records.

03My domain is on Cloudflare. Is there a shortcut?

Yes. When FirstSales detects Cloudflare, press Add to Cloudflare, paste a token scoped to Zone, DNS, Edit on that domain, and apply. The token is masked, used once and never stored. Only missing records are added.

04What is Managed DKIM?

For SMTP/IMAP and relay mailboxes, FirstSales can create your DKIM key and rotate it over time. You add one CNAME record once. Google and Microsoft mailboxes manage DKIM themselves, so they do not show the button.

05I added the records but the check fails. Why?

Usually DNS has not spread yet. Changes can take up to 48 hours. Wait, then press Re-check DNS Records. If it still fails, copy the record again exactly as your Technical tab shows it.

06How is the authentication score worked out?

It is weighted: SPF counts for 34 percent, DKIM and DMARC for 33 percent each. All three passing reaches 100 percent, shown as Fully Authenticated.

07Is authentication required?

Above 5,000 emails a day, yes. Gmail and Yahoo reject unauthenticated bulk mail with error 550-5.7.26. Below that it is strongly recommended, because unauthenticated mail tends to land in spam.

08Will an unfinished setup stop me from sending?

No. The check is advisory and never blocks a send. But mail without authentication often lands in spam or gets rejected, so finish the set before you scale up.

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.