There are several reasons you might need to remove a sending domain from MigoSMTP — rebranding, migrating to a different subdomain, replacing a compromised domain, or freeing up a slot for a different domain. This article covers the safe process for removing a domain, what happens to existing sends, and how to set up a replacement without disrupting ongoing delivery.
Reasons to Remove a Sending Domain
| Scenario | Recommended Action |
|---|---|
| Rebranding — company name change | Add the new domain and verify it before removing the old one to ensure zero downtime |
| Migrating from root to subdomain | Add and verify the new subdomain first; update SMTP/API integrations; then remove the root domain |
| Domain reputation compromised | Add a clean replacement domain immediately; migrate sending; investigate and remediate the compromised domain; remove when clear |
| Freeing a domain slot on current plan | Ensure no active SMTP accounts or applications are using the domain before removing |
| Client domain — client has moved away | Confirm no sends are in queue for that domain; remove and clean up DNS records |
Pre-Removal Checklist
| ✓ | Check Before Removing |
|---|---|
| □ | Identify all SMTP accounts using this domain as the From address |
| □ | Identify all API keys configured to send from this domain |
| □ | Identify all templates using this domain in the From address |
| □ | Check that no messages are currently queued for this domain |
| □ | Export delivery report data for this domain if needed for records |
| □ | Confirm a replacement domain is verified and ready (if applicable) |
| □ | Update all application SMTP configuration to use the replacement domain |
Remove after migration, not before. Never remove the old domain until the replacement is fully set up, verified, and your applications have been updated. Removing the From domain before switching your applications causes immediate send failures.
Step-by-Step: Removing a Domain
- Log in to MigoSMTP → Domain Management.
- Locate the domain you want to remove.
- Click the delete icon or Remove Domain at the end of the domain row.
- A confirmation dialog appears — it lists any SMTP accounts or resources still using this domain.
- If resources are listed, update them to use a different domain first, then return to remove.
- If no resources are listed, type the domain name in the confirmation field and click Confirm Removal.
What Happens When a Domain Is Removed
| Resource | What Happens |
|---|---|
| Queued messages using this domain | Remaining queued messages may fail if the domain is removed before delivery — clear or cancel the queue first |
| SMTP accounts sending from this domain | SMTP accounts remain but From address submissions using the removed domain are rejected |
| Existing delivery logs | Historical delivery logs for messages sent from this domain are retained for the standard 90-day active / 1-year archive period |
| Domain slot | The slot becomes available immediately for a new domain |
| DNS records | MigoSMTP does not remove your DNS records — you must manually delete the SPF, DKIM, DMARC, and tracking CNAME records from your DNS provider |
Cleaning Up DNS After Domain Removal
After removing a domain from MigoSMTP, clean up the corresponding DNS records from your registrar to avoid cluttering your DNS zone:
- Log in to your DNS provider.
- Delete the SPF TXT record at
[yourdomain]. - Delete the DKIM TXT record at
migo._domainkey.[yourdomain]. - Delete the DMARC TXT record at
_dmarc.[yourdomain]. - Delete the tracking CNAME record if you set one up (e.g.
track.[yourdomain]).
Replacing a Domain — Zero-Downtime Migration
To replace one sending domain with another without any interruption to your email delivery:
- Add the replacement domain in MigoSMTP → Domain Management → Add Domain.
- Publish DNS records for the new domain at your DNS provider.
- Verify the new domain and confirm it passes all DNS checks.
- Run a test send from the new domain to confirm everything works.
- Update your application SMTP configuration or API payload to use the new From address on the new domain.
- Update your email templates that have the From address hard-coded to use the new domain.
- Deploy the application change and confirm live sends are going out from the new domain via Delivery Reports.
- Monitor for 24–48 hours to confirm delivery rates are healthy on the new domain.
- Remove the old domain after confirming everything is working on the new domain.
- Clean up old DNS records for the removed domain.