A website launch is also a domain and email launch. A page can look perfect while a missing DNS record, expired certificate, broken redirect, or untested form quietly costs trust and leads. This checklist focuses on the small set of controls a business should verify before announcing a new website, landing page, rebrand, or hosting migration.
Confirm domain ownership and renewal
Verify the registrar account, renewal date, payment method, recovery email, and authorized administrators. Keep at least two trusted people able to recover the domain without sharing a master password. Record the registrar, DNS host, nameservers, and escalation contacts. A domain expiry or accidental nameserver change can take down the website and email at the same time.
Check DNS deliberately
Confirm A, AAAA, CNAME, and redirect records point to the intended production destination. Remove obsolete staging records only after confirming no service still uses them. If you are changing nameservers, compare the complete old zone and new zone—not just the website record. Mail records, verification tokens, and subdomains are easy to omit during a rushed move.
Test HTTPS and certificates
Open the site in a normal browser using both the preferred hostname and any redirecting variant. Confirm HTTPS loads without a certificate warning, the certificate matches the domain, and redirects do not create loops. Check certificate-expiry ownership and renewal method. Test important pages, forms, checkout paths, and any embedded resources after the public DNS change has propagated.
Validate website behavior
Check the homepage, key conversion pages, contact forms, login or account flows, analytics, privacy/terms links, and mobile layout. Submit a test form to an address you control. Confirm automated notifications arrive and do not land in spam. Document the expected response so you can distinguish a form failure from an inbox rule or authentication issue.
Audit email authentication
List every system that sends mail as the domain: mailboxes, website forms, CRM, billing, support, and marketing tools. Verify SPF, DKIM, and DMARC are public and current. Use the email-authentication audit, SPF check guide, and DMARC check guide for the evidence to collect. A website migration can change form delivery or add a new sender even when normal mailbox mail still works.
Plan the DNS change window
Make changes before the public announcement, record the old values, and note TTLs. Avoid making unrelated email, hosting, and design changes at the same moment. After publishing, check independent public DNS lookups and send fresh test messages. If different tools show different values, allow the expected cache window before stacking corrective edits unless you find a clear syntax or host-name error.
Set monitoring and ownership
Assign someone to receive uptime, certificate, expiry, and email-authentication alerts. Give that person a practical escalation path to the registrar, host, DNS provider, and email provider. A launch checklist is successful when it creates ongoing visibility, not just a one-day sign-off.
Final launch review
- Domain and DNS ownership are documented.
- HTTPS works on the intended production URL.
- Forms and transactional messages pass a fresh test.
- SPF, DKIM, and DMARC match current senders.
- Monitoring and renewal alerts reach an accountable owner.
Run Beacon’s free domain check before and after launch to review public email-authentication signals alongside the website checks.
Keep the handoff record
Save the final DNS values, test-message headers, alert contacts, and renewal dates in the launch record. That evidence makes future troubleshooting faster and gives the next owner a reliable baseline.