NameSilo
Verify your domain on NameSilo with Reloop.
NameSilo can use Reloop Auto-populate when nameservers match. Manual steps are always available as a fallback.
Add a domain in Reloop
- Log in to Reloop and add a domain.
- Keep that tab open — every host and value you paste must match Reloop exactly (especially the DKIM key).
Automatic setup (recommended)
NameSilo supports Reloop Auto-populate (Domain Connect). This is usually the fastest path.
Open the domain in Reloop
Go to Domains and open the domain you added.
Enable receiving first (optional)
If you need Reloop to receive mail on this hostname, turn receiving on in the domain settings before Auto-populate so the correct MX rows are included. See Sending vs receiving.
Click Auto populate
Reloop opens NameSilo for consent. Sign in if asked, review the records, and approve.
Verify
Return to Reloop and click Verify. Status should move to active within a few minutes (see propagation).
If Auto-populate fails or you prefer full control, use Manual setup below. Details: Auto-populate DNS and Auto-populate failed.
Manual setup
Log in to NameSilo
Open NameSilo and go to DNS for the domain whose nameservers match dnsowl.com / hostsilo.com.
NameSilo → Domain Manager → DNS Manager.
If Reloop or dig NS yourdomain.com shows a different host, stop and edit that host instead — see Wrong nameservers.
Field mapping
| Reloop | NameSilo field | Example |
|---|---|---|
| Type | Type | TXT / MX / CNAME |
| Name / Host | Name | @, reloop._domainkey, _dmarc, link, … |
| Value / Content | Value | Exact value from Reloop |
| TTL | TTL | Auto or provider default |
| Priority (MX only) | Priority | As 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:
Choose the type
Match Reloop’s type: TXT, MX, or CNAME.
Set the name / host
Copy the host from Reloop (@, reloop._domainkey, _dmarc, link, …).
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.
Save
Save the record, then continue with the next Reloop row.
Typical Reloop rows (always confirm in the dashboard):
| Purpose | Type | Host (typical) | Value (typical) |
|---|---|---|---|
| SPF | TXT | @ | v=spf1 include:reloop.sh -all (or merge into existing SPF) |
| DKIM | TXT | reloop._domainkey | v=DKIM1; k=rsa; p=… (unique per domain) |
| DMARC | TXT | _dmarc | v=DMARC1; p=reject; (or your existing policy) |
| Tracking | CNAME | link | link.reloop.sh |
| Receiving MX | MX | @ or subdomain host | inbound.reloop.sh (when receiving is enabled) |
NameSilo-specific notes
- NameSilo syncs Domain Connect templates from the public registry — prefer Auto-populate when offered.
- Confirm you are editing DNS at NameSilo (not a different host pointed to by custom NS).
Receiving emails
If you enable Receiving on the domain in Reloop, you must publish the inbound MX Reloop shows (typically inbound.reloop.sh).
Complete verification
- Return to Domains in Reloop.
- Open the domain and click Verify.
- Wait until status is active. Most providers update within minutes; allow up to 48–72 hours in rare cases (propagation).
Troubleshooting
Related
Was this page helpful?
- Need help? Contact Support.
- Chat with Reloop developers on Discord.
- Check out our changelog.
- Questions? Contact Sales.
- LLM? Read llms.txt.