Reloop

Beta
Get Started

For the complete documentation index, see llms-docs.txt or the site index llms.txt. Full docs corpus: llms-full-docs.txt. Prefer the markdown version of this page at /docs/guides/connect-domain/dns-records-explained.md. Product capabilities: skill.md. Docs MCP: /docs/mcp. Site MCP: /mcp.

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

PurposeTypical typeExample hostWhat it does
SPFTXT@Authorizes Reloop to send for your domain
DKIMTXTreloop._domainkeyCryptographic signature so receivers trust the message
DMARCTXT_dmarcPolicy if SPF/DKIM fail (Reloop suggests a strict policy)
Sending MXMX@Used in Reloop’s sending/return-path setup as shown in the dashboard
Receiving MXMX@ or your subdomainRoutes inbound mail to Reloop (inbound.reloop.sh) when receiving is on
TrackingCNAMElinkClick/open tracking (link.yourdomain.com → link.reloop.sh)

Hosts and whether MX/tracking appear depend on your domain settings (apex vs subdomain, sending/receiving toggles).

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).

You may only have one SPF TXT on a given host. If you already have SPF (Google, Microsoft, Mailchimp, …), merge Reloop’s include:reloop.sh into that record — do not add a second SPF. See SPF conflicts.

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. If you already have DMARC for Google/Microsoft, review carefully before overwriting — you may keep your existing policy and align later.

MX (mail exchange)

MX records control where inbound mail is delivered.

  • Sending-only: you may still see MX-related rows in Reloop; follow the dashboard. Reloop sending does not require replacing your existing inbox MX if you only send from Reloop.
  • Receiving enabled: Reloop expects MX pointing at inbound.reloop.sh (priority typically 10). That will conflict with another inbox already using MX on the same hostname. Use a separate hostname for Reloop receiving, or see MX conflicts.

Tracking CNAME

Type: CNAME
Host: usually link
Value: link.reloop.sh

Used for branded click/open tracking links (https://link.yourdomain.com/...).

Conflicts if link 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:

  1. Type (TXT / MX / CNAME)
  2. Name / Host — some UIs want @ for the root; others want a blank host or the bare domain
  3. 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.

Was this page helpful?

Edit this page
Find your DNS providerPreviousAdd a domainNext