DNS records Reloop needs
What each Reloop DNS record does — SPF, DKIM, DMARC, MX, and tracking — and how to read them in the dashboard.
When you add a domain, Reloop generates the exact records to publish. Always prefer the dashboard values over examples here. Your DKIM key is unique.
Quick map
| Purpose | Typical type | Example host | What it does |
|---|---|---|---|
| SPF | TXT | @ | Authorizes Reloop to send for your domain |
| DKIM | TXT | reloop._domainkey | Cryptographic signature so receivers trust the message |
| DMARC | TXT | _dmarc | Policy if SPF/DKIM fail — required for verification when Email Sending is on |
| Sending MX | MX | @ or subdomain host | Required when Email Sending is on (reloop.sh) — does not by itself replace your inbox |
| Receiving MX | MX | @ or subdomain host | Routes inbound mail to Reloop (inbound.reloop.sh) when Email Receiving is on (default for new domains) |
| Tracking | CNAME | link or link.<sub> | Click/open tracking → link.reloop.sh (on by default for new domains) |
Hosts and whether MX/tracking appear depend on your domain settings (apex vs subdomain, sending/receiving/tracking toggles). Always copy the host from the Reloop dashboard.
SPF (Sender Policy Framework)
Type: TXT
Example value:
v=spf1 include:reloop.sh -all
SPF lists which servers may send mail as your domain. Reloop’s include is include:reloop.sh (hosted product).
DKIM (DomainKeys Identified Mail)
Type: TXT
Host: usually reloop._domainkey (selector reloop)
Value: looks like:
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A...
The long p= string is your public key. Reloop signs outbound mail with the matching private key. If the TXT is truncated, quoted wrongly, or split incorrectly, verification fails. See DKIM / DMARC typos.
DMARC
Type: TXT
Host: _dmarc
Example value:
v=DMARC1; p=reject;
DMARC tells receivers what to do when authentication fails. Reloop’s default template uses p=reject. When Email Sending is on, a matching DMARC record is required for Reloop verification. If you already have DMARC for Google/Microsoft, you can often keep your existing policy — Reloop checks that a valid DMARC record is present; review carefully before overwriting a production policy.
MX (mail exchange)
Reloop may show two different MX purposes:
- Sending MX → typically
reloop.sh. Required when Email Sending is on. Publishing this record does not require removing your existing inbox MX. - Receiving MX → typically
inbound.reloop.sh. Used when Email Receiving is on (default for new domains). On the same hostname as Google Workspace / Microsoft 365, this can divert or split inbound delivery — turn Receiving off for send-only, or use a separate hostname. See MX conflicts.
Tracking CNAME
Type: CNAME
Host: link on an apex domain; for a Reloop subdomain such as mail.example.com, the host is often link.mail (always copy from the dashboard)
Value: link.reloop.sh
Used for branded click/open tracking links. Click and open tracking are on by default for new domains; disable tracking in Reloop if you do not want this CNAME.
Conflicts if that host already points elsewhere, or if your provider disallows CNAMEs in that spot. See Tracking CNAME issues.
How to read a Reloop dashboard row
For each row, match three things in your DNS UI:
- Type (TXT / MX / CNAME)
- Name / Host — some UIs want
@for the root; others want a blank host or the bare domain - Value — paste exactly; for MX also set Priority
Provider-specific quirks (Cloudflare proxy, GoDaddy host field, Route 53 hosted zone) are in each provider guide.
Related
Was this page helpful?
- Need help? Contact Support.
- Chat with Reloop developers on Discord.
- Check out our changelog.
- Questions? Contact Sales.
- LLM? Read llms.txt.