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/providers/cloudflare.md. Product capabilities: skill.md. Docs MCP: /docs/mcp. Site MCP: /mcp.

Cloudflare

Verify your domain on Cloudflare with Reloop.

Add domain to Reloop

First, log in to Reloop and add a domain.

Reloop — Add domain
Add Domain dialog in Reloop

It is best practice to use a subdomain (for example mail.example.com or team.example.com) instead of the root domain (example.com). A subdomain keeps sending reputation separate and is especially important if you enable receiving with Reloop.

The fastest way to verify your domain on Cloudflare is Auto populate in Reloop. This uses Domain Connect to configure your DNS records.

  1. Go to your Domains page in Reloop and open the domain.
  2. (Optional) If you want to receive emails, turn Receiving on before Auto-populate so the inbound MX is included. Learn more below.
  3. Click Auto populate.
  4. Authorize Reloop in Cloudflare and approve the records.
  5. Return to Reloop — records are written automatically.

That’s it. Your domain will usually verify within a few minutes.

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

Cloudflare — DNS records
Cloudflare DNS records page

If Reloop or dig NS yourdomain.com shows a different host, stop and edit that host instead — see Wrong nameservers.

Add MX SPF record

Click Add record on Cloudflare:

  1. Set the Type to MX.
  2. Set the Name to the host Reloop shows (for a subdomain like team.example.com, Cloudflare often wants team).
  3. Copy the MX value from Reloop into the Mail server field (typically reloop.sh).
  4. Use Auto for TTL.
  5. Set Priority to the value Reloop shows (often 10).
  6. Select Save.
Reloop — Sending MX
Reloop sending MX (SPF) record
Cloudflare — Sending MX
Add sending MX record in Cloudflare

Below is a mapping of the record fields from Reloop to Cloudflare:

CloudflareReloopExample value
TypeTypeMX
NameNameteam (or @ for the root)
Mail serverValuereloop.sh
PriorityPriority10
TTLTTLAuto

Omit your domain from the Name field when Cloudflare appends it. Paste team, not team.example.com.

Do not reuse the same priority for conflicting MX records you must keep. If Priority 10 is already in use on that host, follow Reloop’s UI or use a separate subdomain.

Add TXT SPF record

Click Add record on Cloudflare:

  1. Set the Type to TXT.
  2. Set the Name to the host Reloop shows (same host as the sending MX, e.g. team or @).
  3. Copy the TXT value from Reloop into Content (typically v=spf1 include:reloop.sh -all).
  4. Use Auto for TTL.
  5. Select Save.
Reloop — SPF TXT
Reloop SPF TXT record
Cloudflare — SPF TXT
Add SPF TXT record in Cloudflare
CloudflareReloopExample value
TypeTypeTXT
NameNameteam (or @ for the root)
ContentValuev=spf1 include:reloop.sh -all
TTLTTLAuto

Omit your domain from the Name field when Cloudflare appends it. Paste team, not team.example.com.

Never create a second SPF TXT on the same host. If SPF already exists, merge include:reloop.sh into that record. See SPF conflicts.

Add TXT DKIM record

Click Add record on Cloudflare:

  1. Set the Type to TXT.
  2. Set the Name from Reloop (selector is usually reloop._domainkey). For a subdomain zone at the apex, Cloudflare often needs reloop._domainkey.team.
  3. Copy the full TXT value from Reloop into Content (v=DKIM1; k=rsa; p=…).
  4. Use Auto for TTL.
  5. Select Save.
Reloop — DKIM TXT
Reloop DKIM TXT record
Cloudflare — DKIM TXT
Add DKIM TXT record in Cloudflare
CloudflareReloopExample value
TypeTypeTXT
NameNamereloop._domainkey (or reloop._domainkey.team under the apex zone)
ContentValuev=DKIM1; k=rsa; p=… (unique per domain)
TTLTTLAuto

Omit your domain from the Name field when Cloudflare appends it. Paste reloop._domainkey or reloop._domainkey.team, not the full FQDN ending in .example.com.

Receiving emails

If you want Reloop to receive mail on this hostname, turn Receiving on in the domain settings in Reloop, then click Add record on Cloudflare:

  1. Set the Type to MX.
  2. Set the Name to the host Reloop shows (e.g. team or @).
  3. Copy the MX value from Reloop into Mail server (typically inbound.reloop.sh).
  4. Use Auto for TTL.
  5. Set Priority as shown in Reloop (often 10).
  6. Select Save.
Reloop — Receiving MX
Reloop receiving MX record
Cloudflare — Receiving MX
Add receiving MX record in Cloudflare
CloudflareReloopExample value
TypeTypeMX
NameNameteam (or @ for the root)
Mail serverValueinbound.reloop.sh
PriorityPriority10
TTLTTLAuto

When Reloop’s inbound MX is active on a hostname, Reloop receives mail for that hostname according to MX priority. That can conflict with another inbox already using MX on the same name — prefer a subdomain. See MX conflicts and Sending vs receiving.

Complete verification

Return to Domains in Reloop, open the domain, and click Verify & finish. It may take a few minutes (rarely up to 48–72 hours) — see propagation.

Reloop — Verify & finish
Verify and finish domain setup in Reloop

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.

Reloop — You're all set
Verified domain ready to send in Reloop

Cloudflare-specific notes

  • Keep Reloop mail/auth records on DNS only (grey cloud). Orange-cloud proxy often breaks verification.
  • Optional DMARC and tracking (link CNAME) rows also appear in Reloop when enabled — add them the same way from the dashboard values.

Troubleshooting

If your domain is not successfully verified, try these common fixes.

Was this page helpful?

Edit this page
OverviewPreviousDomain ChiefNext