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/providers/cloudflare.md. Product capabilities: skill.md. Docs MCP: /docs/mcp. Site MCP: https://nuratix.com/mcp.
Cloudflare DNS Setup: Add MX, SPF, DKIM & DMARC Records
Step-by-step: add MX, SPF, DKIM and DMARC records in Cloudflare to verify your domain and send email with Reloop. Copy-paste values for each record.
Add domain to Reloop
First, log in to Reloop and add a domain.

Automatic setup (recommended)
The fastest way to verify your domain on Cloudflare is Auto populate in Reloop. This uses Domain Connect to configure your DNS records.
Auto populate is only on Reloop Cloud. On a self-hosted instance, skip to Manual setup.
- Go to your Domains page in Reloop and open the domain.
- Check Email Receiving before Auto-populate. New domains start with Receiving on, so inbound MX (
inbound.reloop.sh) is usually included. Turn Email Receiving off first if this hostname must keep Google Workspace / Microsoft 365, or use a subdomain. Learn more below. - Click Auto populate.
- Authorize Reloop in Cloudflare and approve the records.
- Return to Reloop and click Verify & finish (setup) or Verify Domain (detail) to start checks.
Verification often finishes within a few minutes after DNS publishes; allow longer if resolvers are slow (propagation).
If Auto-populate fails, use Manual setup below. See also Auto-populate DNS and Auto-populate failed.
Manual setup
If you prefer to add DNS records manually, follow these steps. Always copy Type / Name / Value from your domain page in Reloop. The examples below use placeholders.
Log in to Cloudflare
Log in to your Cloudflare account and open DNS → Records for the domain whose nameservers match *.ns.cloudflare.com.

If Reloop or dig NS yourdomain.com shows a different host, stop and edit that host instead. See Wrong nameservers.
Add TXT SPF record
Click Add record on Cloudflare:
- Set the Type to
TXT. - Set the Name to the host Reloop shows (e.g.
teamor@). - Copy the TXT value from Reloop into Content (typically
v=spf1 include:reloop.sh -all). - Use
Autofor TTL. - Select Save.


| Cloudflare | Reloop | Example value |
|---|---|---|
| Type | Type | TXT |
| Name | Name | team (or @ for the root) |
| Content | Value | v=spf1 include:reloop.sh -all |
| TTL | TTL | Auto |
Add TXT DKIM record
Click Add record on Cloudflare:
- Set the Type to
TXT. - Set the Name from Reloop (selector is usually
reloop._domainkey). For a subdomain zone at the apex, Cloudflare often needsreloop._domainkey.team. - Copy the full TXT value from Reloop into Content (
v=DKIM1; k=rsa; p=…). - Use
Autofor TTL. - Select Save.


| Cloudflare | Reloop | Example value |
|---|---|---|
| Type | Type | TXT |
| Name | Name | reloop._domainkey (or reloop._domainkey.team under the apex zone) |
| Content | Value | v=DKIM1; k=rsa; p=… (unique per domain) |
| TTL | TTL | Auto |
Receiving emails
Email Receiving is on by default for new domains. If it stays on, add the inbound MX in Cloudflare:
- Set the Type to
MX. - Set the Name to the host Reloop shows (e.g.
teamor@). - Copy the MX value from Reloop into Mail server (typically
inbound.reloop.sh). - Use
Autofor TTL. - Set Priority as shown in Reloop (often
10). - Select Save.


| Cloudflare | Reloop | Example value |
|---|---|---|
| Type | Type | MX |
| Name | Name | team (or @ for the root) |
| Mail server | Value | inbound.reloop.sh |
| Priority | Priority | 10 |
| TTL | TTL | Auto |
Complete verification
Return to Domains in Reloop. On the setup page click Verify & finish; on the domain detail page click Verify Domain (menu: Re-verify DNS). It may take a few minutes (rarely up to 48–72 hours). See propagation.

When verification succeeds, Reloop shows You're all set! (Domain added → Verified → Ready to send). Your domain is verified and you are good to go.

Cloudflare-specific notes
- Keep Reloop mail/auth records on DNS only (grey cloud). Orange-cloud proxy often breaks verification.
- DMARC is required for verification when Email Sending is on (keep an existing policy if you already have one). Tracking CNAME is on by default for new domains. The host is usually
linkon apex, orlink.<sub>for subdomains; copy from the dashboard.
Troubleshooting
If your domain is not successfully verified, try these common fixes.
Related
Was this page helpful?