Your sending domain is the domain in your From email address — for example, if you send from hello@yourcompany.com, your sending domain is yourcompany.com. Adding and verifying a domain in MigoSMTP is the most important configuration step before you can send email reliably. This article walks through the complete process from start to finish.
Before You Start — What You Need
- A domain you own (e.g.
yourcompany.com) — purchased from a domain registrar such as GoDaddy, Namecheap, Google Domains, Cloudflare, or a hosting provider. - Access to your domain's DNS settings (your registrar or DNS provider control panel).
- Approximately 15 minutes — plus time for DNS propagation (30 minutes to 48 hours, usually under 1 hour).
Use a subdomain for sending: It is best practice to send from a subdomain (e.g.
mail.yourcompany.com or email.yourcompany.com) rather than your root domain (yourcompany.com). This protects your main domain's reputation — if your email sending reputation is harmed, it does not affect your website's deliverability.
Step 1 — Add Your Domain in MigoSMTP
- Log in to MigoSMTP via the Rackwave portal SSO.
- Click Domain Management in the left sidebar.
- Click Add Domain.
- Enter your sending domain (e.g.
mail.yourcompany.com). - Click Add.
- MigoSMTP generates the DNS records you need to publish — do not close this page yet.
Step 2 — Publish the Required DNS Records
MigoSMTP requires three DNS records to be published before it can verify your domain. Each record serves a specific authentication purpose:
| Record | Type | Host / Name | Value | Purpose |
|---|---|---|---|---|
| SPF | TXT | mail.yourcompany.com | v=spf1 include:migosmtp.com ~all | Authorises MigoSMTP to send on your behalf |
| DKIM | TXT | migo._domainkey.mail.yourcompany.com | v=DKIM1; k=rsa; p=[key from dashboard] | Digitally signs outgoing emails |
| DMARC | TXT | _dmarc.mail.yourcompany.com | v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com | Sets policy and enables reporting |
Copy exact values from your dashboard. MigoSMTP generates the precise DKIM public key unique to your domain. Do not type it manually — copy it directly from the Domain Management page to avoid errors. A single incorrect character in a DKIM key causes all authentication to fail.
How to Add DNS Records — General Steps
- Log in to your domain registrar or DNS provider control panel (e.g. GoDaddy, Namecheap, Cloudflare).
- Navigate to DNS Management or DNS Records for your domain.
- Add each of the three records above using the Add Record form.
- Set the TTL (Time to Live) to 3600 (1 hour) or the lowest value your provider allows.
- Save each record.
DNS Setup — Provider-Specific Notes
| Provider | Note |
|---|---|
| Cloudflare | Set DNS records to DNS Only (grey cloud) — not Proxied (orange cloud). Proxied records cannot be used for email authentication. |
| GoDaddy | GoDaddy auto-appends your domain to the Host field. Enter only the subdomain part — e.g. for migo._domainkey.mail.yourcompany.com, enter migo._domainkey.mail. |
| cPanel Hosting | Use the Zone Editor in cPanel. For subdomain records, include the full record name including your domain. |
| Google Domains (now Squarespace) | Go to DNS → Manage → Custom records. Use the full record hostname including domain name. |
Step 3 — Verify Your Domain
- Return to MigoSMTP → Domain Management.
- Find your domain in the list — it will show status Pending Verification.
- Click Verify Domain.
- MigoSMTP checks for your SPF and DKIM records in DNS.
- If all records are found correctly, the status changes to Verified.
DNS propagation delay: If verification fails immediately after publishing records, wait 15–30 minutes and try again. DNS changes take time to propagate globally. In most cases propagation completes within 30–60 minutes, but can take up to 48 hours in rare cases. You can check propagation status using dnschecker.org.
Understanding Domain Status Indicators
| Status | Meaning | Action |
|---|---|---|
| Pending | Domain added but not yet verified | Publish DNS records then click Verify |
| Verified | All records found — domain ready for sending | None — you can start sending |
| Failed | One or more DNS records not found or incorrect | Check records in your DNS panel — see troubleshooting below |
| SPF Partial | SPF record found but DKIM not yet propagated | Wait for DKIM propagation — verify again in 30 minutes |
Troubleshooting Domain Verification Failures
| Problem | Likely Cause | Fix |
|---|---|---|
| SPF not found | Record not yet published or published at wrong hostname | Double-check the hostname — use the exact value from the MigoSMTP dashboard; avoid adding extra dots or spaces |
| DKIM not found | DKIM hostname too long for some providers; DNS not propagated | Verify the full hostname was saved correctly; check propagation at dnschecker.org; wait up to 1 hour |
| SPF too many lookups | Existing SPF record already at the 10-lookup limit | Flatten your SPF record — remove unused includes; see: SPF Configuration |
| Cloudflare orange-cloud proxying | DNS record is proxied through Cloudflare CDN, hiding the real value | Set the DKIM and SPF records to DNS Only (grey cloud) in Cloudflare |