Cloudflare

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.

1. Go to your Domains page in Reloop and open the domain.
2. 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.
3. Click Auto populate.
4. Authorize Reloop in Cloudflare and approve the records.
5. 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 — 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 Sending MX 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.

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

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.

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.

Receiving emails

Email Receiving is on by default for new domains. If it stays on, add the inbound MX in 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.

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 — host is usually link on apex, or link.<sub> for subdomains; copy from the dashboard.

Troubleshooting

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

Related

• DNS records explained
• Manual DNS setup
• Auto-populate DNS
• All provider guides