Five areas to check after registering a domain, before a hosting migration or when business email stops arriving. Each section includes concrete steps and ways to verify them.
01
Domain ownership, protection and renewal
Problems often start when only a former contractor can access the registrar account or the registrant contact mailbox stops working.
- Confirm who controls the registrar account and registrant mailbox. Enable two-factor authentication.
- Use a transfer lock where supported and store recovery information securely.
- Enable auto-renewal, verify the payment method and set reminders 30, 14 and 7 days before expiry.
- Check registry-specific transfer restrictions before changing registrars.
How to verify: Locate the expiry date, transfer lock, 2FA, renewal settings and registrant contacts in your registrar account.
02
Move hosting without breaking DNS or email
Changing web hosting, domain registration and email hosting are separate operations. Each requires its own migration checklist.
- Back up files, databases, environment configuration and current DNS records.
- Test the new hosting environment before cutover, including forms, checkout, login and SSL certificates.
- Lower the affected DNS TTL ahead of migration where possible and allow old caches time to expire.
- Avoid changing MX, SPF, DKIM or DMARC records unless email is also moving.
- Compare DNS responses after switching and test incoming and outgoing mail.
How to verify: Check site functionality, DNS answers, HTTPS, forms and sending and receiving test emails.
03
Email authentication: SPF, DKIM and DMARC
Mailbox providers consider sender authentication, domain reputation, message content and recipient responses.
- Publish one valid SPF policy per DNS hostname, covering every legitimate sending service.
- Enable DKIM signing with your mail provider and publish the DNS records it provides.
- Start DMARC in monitoring mode (p=none), check legitimate mail flows, then gradually enforce quarantine or reject.
- Avoid purchased lists and sudden bulk campaigns from a fresh domain. Respect recipients’ marketing preferences.
- Monitor bounces, spam complaints and email authentication results.
How to verify: Send tests to different mailbox providers and inspect SPF, DKIM and DMARC results in the message headers.
04
Backups and tested restores
A backup only matters if you can restore a working site from it, including databases and order history.
- Follow the 3-2-1 backup principle: three copies, two media types, one off the production host.
- Restrict backup access and encrypt off-site copies.
- Keep several restore points rather than overwriting yesterday’s backup.
- Document restoration of files, database, configuration, DNS and key services.
How to verify: Test a restore on a staging environment at least once a quarter and record the recovery time.
05
Updates, HTTPS and uptime monitoring
A working domain does not protect a website from outdated plugins, weak credentials or unnoticed downtime.
- Update your CMS, PHP, libraries and plugins after testing and backing up changes.
- Use HTTPS with automatic certificate renewal and test redirects after migrations.
- Enforce two-factor authentication and least-privilege access.
- Monitor availability, certificate expiry, unexpected DNS changes and admin sign-in failures.
- Keep a short change log and a tested rollback procedure.
How to verify: Check TLS, pending updates and monitoring alerts from a private browser session.