Domain Email Setup Checklist Before You Launch Hosting
A checklist for protecting business email while connecting a domain to website hosting, including MX, SPF, DKIM, and DMARC.
Email records deserve special attention
Many website launches accidentally break email because nameservers are changed without copying mail records. Business email depends on DNS, usually through MX records and authentication records. If those records disappear, messages can bounce or land in the wrong place.
Before connecting hosting, identify the email provider. It may be Google Workspace, Microsoft 365, a mailbox from the registrar, or another service. Then capture the exact records that provider requires.
- Find current MX records before changing nameservers.
- Record SPF, DKIM, and DMARC TXT records.
- Ask the business owner which inboxes are active.
- Schedule launch work when email disruption would be least harmful.
Authentication improves deliverability
SPF, DKIM, and DMARC help receiving mail servers decide whether messages from your domain are legitimate. They are not only technical extras. They protect reputation and reduce the chance that business email lands in spam.
When DNS changes during hosting setup, authentication records should move with the domain. If a new DNS zone is created without those records, outbound email may still send but perform worse.
- SPF lists services allowed to send for the domain.
- DKIM signs messages so recipients can verify them.
- DMARC tells recipients how to handle suspicious messages.
- Review authentication after adding CRMs, newsletter tools, or invoicing platforms.
Test both sending and receiving
After hosting and DNS changes, send test messages in both directions. Test from the business account to an outside address, then from an outside address back to the business account. Also test forms on the website because form notifications may use a different sending path.
If form messages are unreliable, use authenticated SMTP or a transactional email service. Website hosting can display the form, but reliable delivery often requires proper email configuration.
- Send test emails to and from external accounts.
- Submit every important website form after launch.
- Check spam folders during testing.
- Document the final email provider and DNS records.