Key takeaway
Authentication lets receivers check that mail really comes from your domain. It cannot make unwanted mail welcome, so set it up first and then grow volume slowly.
A domain is ready for outreach when four kinds of DNS record are in place: SPF and DKIM, which let receivers check that a message really comes from you; DMARC, which tells them how to treat mail that fails those checks; and MX, which makes sure replies reach a mailbox. After that, it needs patience. Google’s advice to senders is to start with a low volume and increase it slowly.
This guide explains what each record does, the mistakes that quietly break them, and how to decide whether outreach should have a domain of its own. Your mailbox provider gives you the exact values; this guide helps you check that they are in place and make sense.
Choose the domain your outreach will use
Every message carries a domain in its From address, and mailbox providers build a picture of that domain from how its mail is received. Decide which domain that will be before you create mailboxes, because it is hard to change once replies and reputation are attached to it.
Mailbox providers do not require a separate domain for outreach, and none of the sources below recommends one specifically. They do recommend keeping different kinds of mail apart: Google suggests using the same From address for messages of the same category, and Yahoo suggests separating types of email by IP address or DKIM domain. A common way to apply that idea is a second domain for outreach, so that invoices, password resets and everyday team mail do not depend on how prospecting is received.
If you choose a second domain, make it plainly yours: a recognizable version of your company name, a website that leads to your main site, and mailboxes your team actually reads. A subdomain does not keep volume separate for Gmail’s bulk-sender count, because Google counts mail from subdomains toward the primary domain.
Publish the four records
Your mailbox provider, and any service that sends on your behalf, gives you the values to publish. Add them where your domain’s DNS is hosted, and know what each one is for, so you can spot when something is missing.
| Record | What it does | Where it lives |
|---|---|---|
| SPF | Lists the servers allowed to send mail for your domain | One TXT record on the domain, starting with v=spf1 |
| DKIM | Publishes the key receivers use to verify your messages’ signatures | A TXT record at selector._domainkey, with the selector your provider gives you |
| DMARC | Says how receivers should treat mail that fails authentication, and where to send reports | A TXT record at _dmarc on the domain |
| MX | Tells other mail servers where to deliver mail for your domain, including replies | MX records that point to your mailbox provider |
Keep SPF to one record and ten lookups
A domain must publish only one SPF record. When a new service asks you to add SPF, merge its part into the existing record instead of creating a second one: the SPF standard tells receivers to return an error, not a pass, when they find more than one.
SPF also caps the DNS lookups a check may trigger. The include, a, mx, ptr and exists mechanisms and the redirect modifier count toward a limit of 10, and a record that needs more fails with an error. An included service can use several lookups of its own, so remove services that no longer send for you before you add new ones.
Switch on DKIM and start DMARC in monitoring mode
DKIM has two halves. Your provider signs each outgoing message, and the public key you publish lets receivers verify the signature. With some providers, publishing the key is not enough and you also need to switch signing on in their admin settings. For mail to personal Gmail accounts, Google requires a DKIM key of at least 1024 bits.
DMARC connects both checks to the address the recipient sees. A message passes when SPF or DKIM passes for a domain that matches the one in the From address. That match is called alignment, and in the default relaxed mode a subdomain of the same domain counts.
Start with p=none and a rua address for aggregate reports. With p=none you express no preference about failing mail, but the reports still show which services send as your domain and whether they pass; the DMARC standard calls this monitoring mode. Gmail and Yahoo accept p=none from bulk senders. Move to quarantine, which marks failing mail as suspicious, or reject, which marks it as an invalid use of your domain, only once the reports show that every legitimate sender passes.
Host: _dmarc.example.net Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.net
Make replies and visits land somewhere real
Check that the MX records point to the mailbox provider you actually use, and that someone reads every outreach mailbox. A reply that bounces or sits unread costs you the conversation the campaign was meant to start.
Give the domain a website, or forward it to your main site, so a recipient who checks the domain finds your company. Send under real names, and keep the From name, signature and website consistent with each other.
Gmail and Yahoo also require valid forward and reverse DNS for sending servers, and Gmail requires an encrypted (TLS) connection. When you send through a hosted mailbox provider, those belong to the provider’s servers; if you run your own sending server, they are yours to set up.
If your mailboxes are connected to ScaleYourOutreach as senders, each domain’s Domain Health tab checks mail routing, SPF, DKIM, DMARC and website forwarding, along with evidence from real email your connected senders have sent.
Increase volume gradually
A new domain has no sending history. Google’s guidance is to start with a low volume sent to engaged recipients, increase it slowly, send at a consistent rate and avoid bursts. It warns that suddenly doubling volume can lead to rate limiting or a drop in reputation, and that the more you send, the more slowly you should increase.
Cold outreach has no engaged recipients yet, which makes the first sends the place where list quality matters most. Start with your clearest fits, verified addresses and your most relevant message, then read the replies, bounces and complaints before adding more.
The provider guidance cited here gives no safe daily number for a new domain, so treat any schedule you are given as an assumption to test. Google treats a sender that reaches close to 5,000 messages a day to personal Gmail accounts as a bulk sender, permanently, with stricter rules; this guide explains what Gmail and Yahoo require from senders.
Check everything before the first campaign
Run through this list for every domain before it sends outreach:
- Exactly one SPF record, covering every service that sends as the domain.
- DKIM signing switched on, with a key of at least 1024 bits.
- A DMARC record at _dmarc with p=none and a reporting address.
- MX records that point to mailboxes someone reads.
- A website on the domain, or a redirect to your main site.
- A test message to an address you control, with SPF, DKIM and DMARC shown as passing in its headers.
Then start with a small campaign and read what comes back. When the first results look right, you can automate the work step by step without losing sight of the exceptions.
Sources
- RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1 · RFC Editor
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures · RFC Editor
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) · RFC Editor
- Email sender guidelines · Gmail Help
- Email sender guidelines FAQ · Gmail Help
- Sender requirements and recommendations · Yahoo Sender Hub
A general guide to email authentication. Use the exact values your mailbox provider gives you, and check its current documentation before you change DNS.