Skip to content
DMARC Pulse

Email senders

Front DMARC setup: SPF, DKIM and strict alignment

Which Front channels need SPF and DKIM records, why strict SPF alignment fails with Front, and the DNS entry mistakes that block verification.

SPF include for Front

Front does not document an SPF include.

DKIM for Front

Selectors
Front does not document this.
How to enable it
One TXT record under your own domain, for SMTP forwarding channels only. Copy its name and key from the Deliverability tab in Front. Front's example uses fnt._domainkey and warns that your values will differ.

Front 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 Front’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.

Envelope-from (Return-Path)
Front does not document this.

Sending ranges of Front

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

Front does not document this.

Does your domain authorize Front?

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

Front documentation

How it authenticates

Front DMARC setup depends on the channel type. Channels on Gmail sync or Office 365 sync send through those providers' APIs, so Front asks for no DNS records. Your Google or Microsoft setup covers authentication there.

SMTP forwarding channels, Google Groups, and Gmail or Office 365 channels set up with SMTP forwarding need three new records on each domain you send from. Front authorizes SendGrid to send for these channels. A company admin copies the values from the Deliverability tab under Security, then clicks Check DNS settings.

SPF (Sender Policy Framework) lists the servers allowed to send for a domain. DKIM (DomainKeys Identified Mail) signs each message. Front's example screenshots show an MX record and v=spf1 include:sendgrid.net ~all on front-mail.example.com, plus a DKIM key at fnt._domainkey.example.com. Front warns that your values will differ, so copy what your account shows.

The DKIM key sits under your own domain, so the signature can give DMARC the one aligned pass it needs. See DMARC alignment for how that match works. The records also remove "via sendgrid.net" from your From address.

What to watch for

Front says its SMTP channels and required SPF records fail strict SPF alignment. With the aspf tag set to aspf=s, DMARC depends on DKIM alone. Front says relaxed alignment works and that stating aspf=r explicitly resolves some delivery problems.

Leave your existing records alone. Front's MX sits on the front-mail host and does not change inbound mail, and its SPF record is separate from the one on your main domain.

Entering the records by hand needs care. Most DNS providers need the MX value without the leading 100 and the final period. For the other two names, enter only the part before your domain, such as front-mail.

DreamHost, HostGator, SiteGround and Wix cannot create the MX record. Front recommends custom SMTP for those channels.

Confirm the result with the DMARC checker. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Which Front channels need SPF and DKIM records?
SMTP forwarding channels, Google Groups, and Gmail or Office 365 channels set up with SMTP forwarding. Channels on Gmail sync or Office 365 sync use those providers' APIs, so Front asks for no records.
Which DKIM selector does Front use?
Front's text does not name one. Its example screenshots show fnt._domainkey, and Front warns that your values will differ. Copy the name from the Deliverability tab.
Does Front work with aspf=s in my DMARC record?
Front says its SMTP channels and required SPF records fail strict SPF alignment. DMARC can still pass on an aligned DKIM signature, but Front says relaxed alignment, aspf=r, is the mode that works.
Do I have to change my existing MX or SPF record for Front?
No. Front asks for three new records and says not to modify existing ones. Its MX record sits on the front-mail host, so it does not affect inbound mail to your domain.
What if my DNS provider cannot create Front's MX record?
Front names DreamHost, HostGator, SiteGround and Wix as providers that do not support it. It recommends custom SMTP for those channels, so mail goes out through your own servers.

Sources consulted

RFC 6376 §3.6.2.1
checked 2026-11-09

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.