Skip to content
DMARC Pulse

Email senders

SparkPost DMARC setup: SparkPost and Bird Email

Separate SparkPost account authentication from Bird Email setup. Check DKIM, the bounce domain and your existing DMARC policy before changing DNS.

SPF include for SparkPost (Bird)

SparkPost (Bird) does not document an SPF include.

DKIM for SparkPost (Bird)

Selectors
SparkPost (Bird) does not document this.
How to enable it
Use the DKIM selector and public DNS value from your own account. SparkPost Sending Domains API configuration and Bird Email DNS instructions are separate; do not copy example selectors.

SparkPost (Bird) signs with your domain

The signature carries your domain in d=, so DKIM can align with your From address and pass DMARC on its own.

Envelope-from and SPF alignment

SPF counts for DMARC only when this domain matches the domain in your From address. If it is SparkPost (Bird)’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.

Envelope-from (Return-Path)
Copy the bounce-domain configuration for your account and product.

Sending ranges of SparkPost (Bird)

Use these to recognize SparkPost (Bird) in your reports. They change over time, so do not copy them into your SPF record.

2 of 2
  • 147.253.208.0/20
  • 192.174.80.0/20

Updated 2026-11-15

Does your domain authorize SparkPost (Bird)?

Enter your domain. The SPF Checker reads your record and names the senders it authorizes.

SparkPost (Bird) documentation

Bird: DKIM, SPF & DMARC
checked 2026-11-09
Bird: Sending domains
checked 2026-11-09
Bird: Email deliverability
checked 2026-11-09
Bird: What is SPF?
checked 2026-11-09

How it authenticates

SparkPost DMARC setup depends on which product your account uses. SparkPost's Sending Domains API and Bird Email have separate authentication instructions. A Bird Email requirement must not be assumed to apply to an existing SparkPost integration.

The SparkPost API documents DKIM configuration with a selector, public key and private key. Publish the public DNS value for your account; never publish a private key. Its bounce-domain verification uses CNAME or, for Enterprise accounts, MX. Copy the target for your account and region rather than a Bird Email example.

Bird Email requires three verified records before sending: DKIM, a return-path CNAME and DMARC. Its return-path host defaults to send. under the sending domain. That CNAME provides SPF authentication without an include at the domain apex. Use the DKIM checker with your actual selector.

What to watch for

If your domain already has DMARC, preserve its single existing policy and report addresses. Bird Email accepts an inherited parent-domain policy too. For a new policy, publish one TXT at _dmarc, starting with p=none and a rua mailbox you monitor.

A return-path subdomain aligns with a parent From domain in relaxed mode. Under aspf=s, those different names do not align. Check that DKIM passes and aligns with From before enforcing a policy. Keep the DNS values from the product you actually use.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Does SparkPost require a DMARC record?
Bird Email requires verified DKIM, a return-path CNAME and DMARC before sending. The separate SparkPost Sending Domains API reference does not list DMARC as a verification requirement.
Is scph0316 a fixed SparkPost DKIM selector?
No. It is an example in the SparkPost API reference. Use the DKIM selector and public key configured for your own sending domain.
Should I add Bird Email to my root SPF record?
Bird Email uses the authenticated return-path CNAME for SPF. Its documentation says no SPF record is needed at the apex for this path. Preserve SPF entries needed by other services.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.