Disclosure: I work on LaunchReach, which has guided SPF/DKIM/DMARC setup for sending from your own domain. It is mentioned near the end. The steps below work with any email provider.
You have a launch coming. You have written the announcement and built a list. Before you hit send, there is one boring job that decides whether the email reaches inboxes or ends up in spam: authenticating your sending domain.
Three DNS records do this: SPF, DKIM and DMARC. This is what each one does and how to check them, written for a founder who would rather not become a mail admin.
The short version
- SPF lists which servers may send mail for your domain.
- DKIM adds a cryptographic signature to each message, so receivers can verify it was authorised by your domain and not altered.
- DMARC tells receivers what to do when SPF and DKIM checks fail to line up with your visible From domain, and where to send reports.
All three are TXT records (DKIM is sometimes a CNAME, depending on the provider) that you add in your DNS host: Cloudflare, your registrar, Route 53, and so on.
Step 0: decide what you are sending from
Pick the exact From address, for example hello@yourproduct.com. Decide also whether you will send launch mail from your root domain or a subdomain such as mail.yourproduct.com. A subdomain keeps launch-campaign reputation separate from your day-to-day email. Either choice is valid; just be consistent when you set up the records.
List every service that sends mail as your domain: your mailbox provider, your product's transactional email, your newsletter or campaign tool. Each one needs to be covered, and this matters most for SPF.
Step 1: SPF
SPF is a single TXT record at the domain you send from. It looks like this:
yourproduct.com. TXT "v=spf1 include:_spf.google.com include:sendprovider.example ~all" How to read it:
-
v=spf1marks it as SPF. - Each
include:authorises a provider's servers. Your email provider gives you the exact value to use. -
~allis a soft fail for anything not listed.-allis a hard fail. Many people start with~alland tighten later.
Common mistakes:
- Two SPF records on one domain. There must be only one. If you add a second provider, merge it into the existing record.
- Too many lookups. SPF allows 10 DNS lookups in total, and each
include:can consume some. If you stack many services, you can exceed the limit and SPF fails. - Forgetting a sender, like your transactional mail service, so those messages start failing.
Step 2: DKIM
With DKIM, your sending provider signs each message with a private key. You publish the matching public key in DNS so receivers can check the signature.
Your provider will give you a record name and value, typically something like:
selector1._domainkey.yourproduct.com. TXT "v=DKIM1; k=rsa; p=MIGfMA0..." The part before ._domainkey is the selector. Different providers use different selectors, so you can have several DKIM records side by side without conflict. Some providers ask you to create CNAMEs instead, which lets them rotate keys for you.
Common mistakes:
- Pasting the key with line breaks or stray quotes added by your DNS host's editor.
- Putting the record on the wrong name, for example adding
yourproduct.comtwice to a host that appends the domain automatically. - Sending before the record has propagated.
Step 3: DMARC
DMARC sits on top of the other two. It checks that the domain authenticated by SPF or DKIM matches the domain in your visible From address (this is called alignment), and it sets a policy.
The record lives at _dmarc.yourproduct.com:
_dmarc.yourproduct.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourproduct.com" -
p=nonemeans monitor only. Nothing is rejected, but you get reports. -
p=quarantineasks receivers to treat failures as suspicious. -
p=rejectasks them to refuse failures. -
ruais where aggregate reports are sent.
A sensible path for a small team: start at p=none, read the reports for a while to confirm all your legitimate senders pass, then move to quarantine and eventually reject. Jumping straight to reject before you have found every sender is how people block their own invoices.
Step 4: check before you send
Do not trust the green tick in a dashboard alone. Verify from the outside.
Look up the records directly:
dig TXT yourproduct.com +short dig TXT selector1._domainkey.yourproduct.com +short dig TXT _dmarc.yourproduct.com +short Confirm you see exactly one SPF record, the DKIM key, and the DMARC policy.
Send a real test message. Send to a mailbox you control at a different provider and open the full message headers. Look for the Authentication-Results header and check that it shows spf=pass, dkim=pass and dmarc=pass. Also confirm that the domain in the DKIM signature (d=) and the SPF-authenticated domain match your From domain, since that is what alignment means.
Pre-send checklist:
- One SPF record, covering every sender.
- DKIM published and verified for the sending provider.
- DMARC record present, at least
p=none, with a report address. - A test email shows pass for all three in the headers.
- The From address matches the authenticated domain.
- Reply-to is a mailbox someone actually reads.
- Your unsubscribe link works.
The last two are not DNS, but they matter for the same reason: receivers watch how people react to your mail.
What authentication does not do
Passing SPF, DKIM and DMARC does not guarantee inbox placement. It removes a reason for filters to distrust you. Content, list quality, and who you send to still count. Only email people who have a reason to expect it, and keep your sending volume steady rather than jumping from nothing to a large blast on launch day.
Where LaunchReach fits
If you would rather not hand-edit DNS from documentation, LaunchReach includes email sending from your own domain with guided SPF, DKIM and DMARC setup, a drag-and-drop builder and AI-drafted launch announcements. The records themselves are the same ones described above; the guided setup is a way to be walked through them. Email has daily and monthly allowances, and sending pauses when they are used up, with no overage charges. The 7-day Growth trial is $1 and nothing renews automatically.
Whichever tool you use, run the header check on a test email first. It takes a few minutes and tells you far more than a dashboard status does.
If you have hit a DNS gotcha during setup that is not covered here, share it in the comments.
Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com
