Email senders
Gorgias DMARC setup: DKIM, SPF and alignment
Which DNS records Gorgias asks for, how the gor and gor2 DKIM selectors work, and why its suggested DMARC policy needs care on a shared domain.
SPF include for Gorgias
Gorgias does not document an SPF include.
DKIM for Gorgias
- Selectors
- gor gor2
- How to enable it
- Two CNAME records on your domain, at gor._domainkey and gor2._domainkey, pointing to values Gorgias shows for your account. Two keys allow rotation without downtime. Some accounts instead get one DKIM TXT record whose value starts with k=rsa;.
Gorgias does not document which domain it signs with
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Gorgias’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A host on your domain starting with em, set by the custom return path CNAME that Gorgias shows for your account
Sending ranges of Gorgias
Use these to recognize Gorgias in your reports. They change over time, so do not copy them into your SPF record.
Gorgias does not document this.
Does your domain authorize Gorgias?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Gorgias documentation
- Gorgias: Verify your domain to send email from Gorgias
- checked 2026-11-09
- Gorgias: Domain verification FAQ and troubleshooting
- checked 2026-11-09
How it authenticates
Gorgias DMARC setup starts under Settings > Channels > Email, where you pick the address and open Verify Domain. Only admins see the values, and one verification covers every address on that domain. Gorgias requires it for automatic forwarding and strongly recommends it for a direct integration on a custom domain.
Most accounts see CNAME records, which point one DNS name at another. gor._domainkey and gor2._domainkey carry DKIM (DomainKeys Identified Mail), the signature on each message. Two keys let Gorgias rotate them without downtime. A third CNAME, on a host starting with em, is the custom return path, the address that receives bounces. Some accounts get TXT values instead: SPF (Sender Policy Framework) at @, and DKIM with a value starting k=rsa;.
The cited Gorgias articles do not state the signing domain. Send a test and read d= in DKIM-Signature to confirm DMARC alignment.
What to watch for
Gorgias suggests quarantine or reject; applying them before all senders align can disrupt mail. It does not say whether its status check accepts p=none. Preserve existing DMARC and report addresses. For a first policy, monitor at p=none before you tighten the policy.
Already have a DMARC record? Edit it. Two records at _dmarc are both discarded, so receivers treat that name as having no DMARC record. The TXT flow has the same trap: merge the Gorgias value into your existing SPF record, because two SPF records produce a permanent error.
A verified domain lets Gorgias fall back to its own Email Service Providers when a direct send fails. Gorgias does not name them, so unfamiliar sources in your reports may be this fallback.
Records you added for Klaviyo or another app do not cover Gorgias. Allow up to 72 hours, then test selectors gor and gor2 with the DKIM checker.