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

AWS Route 53

Verify your domain on AWS Route 53 with Reloop.

Add Reloop’s DNS records in AWS Route 53 using the values from your domain page in Reloop.

Add a domain in Reloop

  1. Log in to Reloop and add a domain.
  2. Keep that tab open — every host and value you paste must match Reloop exactly (especially the DKIM key).

Reloop works with the root domain, a subdomain, or both — for example example.com, mail.example.com, or updates.example.com.

Manual setup

Log in to AWS Route 53

Open AWS Route 53 and go to DNS for the domain whose nameservers match awsdns-.

Route 53 → Hosted zones → your zone → Records.

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

Field mapping

ReloopAWS Route 53 fieldExample
TypeTypeTXT / MX / CNAME
Name / HostName@, reloop._domainkey, _dmarc, link, …
Value / ContentValueExact value from Reloop
TTLTTLAuto or provider default
Priority (MX only)PriorityAs shown in Reloop (often 10)

Omit your domain from the Name/Host field when the provider appends it automatically. Paste reloop._domainkey or link, not reloop._domainkey.example.com.

Add the records from Reloop

For each required row on the Reloop domain page:

1

Choose the type

Match Reloop’s type: TXT, MX, or CNAME.

2

Set the name / host

Copy the host from Reloop (@, reloop._domainkey, _dmarc, link, …).

3

Paste the value

Copy the value exactly. For MX, also set Priority as shown (often 10). If priority 10 is already used by another MX you must keep, use the next free value only when Reloop’s UI allows it — otherwise use a subdomain.

4

Save

Save the record, then continue with the next Reloop row.

Typical Reloop rows (always confirm in the dashboard):

PurposeTypeHost (typical)Value (typical)
SPFTXT@v=spf1 include:reloop.sh -all (or merge into existing SPF)
DKIMTXTreloop._domainkeyv=DKIM1; k=rsa; p=… (unique per domain)
DMARCTXT_dmarcv=DMARC1; p=reject; (or your existing policy)
TrackingCNAMElinklink.reloop.sh
Receiving MXMX@ or subdomain hostinbound.reloop.sh (when receiving is enabled)

Never create a second SPF TXT on the same host. Merge include:reloop.sh into the existing SPF. See SPF conflicts.

AWS Route 53-specific notes

  • Edit the hosted zone whose NS match the public nameservers (awsdns-).
  • For MX, set the Priority field separately from the Value.

Receiving emails

If you enable Receiving on the domain in Reloop, you must publish the inbound MX Reloop shows (typically inbound.reloop.sh).

When Reloop’s 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 — use a separate hostname for Reloop receiving if needed. See MX conflicts and Sending vs receiving.

Complete verification

  1. Return to Domains in Reloop.
  2. Open the domain and click Verify.
  3. Wait until status is active. Most providers update within minutes; allow up to 48–72 hours in rare cases (propagation).

Troubleshooting

Was this page helpful?

Edit this page
PorkbunPreviousSquarespaceNext