Domain & DNS Pre-launch Checklist: Step-by-step Review

Checking a domain and DNS goes beyond "it just needs to load." This checklist covers ten items across five categories—ownership, resolution, HTTPS, email, and o…

Insights:Domain & DNS Pre-launch Checklist: Step-by-step Review

Before going live, check DNS — the biggest mistake is only verifying whether the site loads in your browser. If it opens for you, that might just be local cache; switching networks or regions could yield completely different results.

The 10 items below are checked in order, each with an explicit passing criterion. Run the full check one day before launch, then again on launch day.

I. Ownership & Renewal

1. The domain is under the correct account, accessible, and renewable.

Passing standard: Able to log into the registrar backend; domain status normal; renewal method valid; expiration date recorded and assigned to someone.

Failing signals: Domain is in a departed colleague's account; renewal reminders go to a rarely-used email; WHOIS info does not match the actual entity.

2. Registrar lock and transfer password are properly managed.

Passing standard: Domain lock is enabled; transfer password is generated only when needed and reset afterward; two-factor authentication is enabled on the account.

Failing signals: Transfer password sits in chat history long-term; multiple outsourced teams all have registrar account access.

II. DNS Records

3. NS records point to the correct DNS provider, and both NS records are functional.

Passing standard: dig NS returns NS records matching the admin panel; both NS records resolve; no leftover NS records from the previous provider remain.

Failing signals: Only one NS was changed; old and new providers coexist; NS records were updated but the record set was not copied over.

4. Both the root domain and www have A/AAAA or CNAME records pointing to the current server.

Passing standard: Both addresses load; resolutions point to the current server IP; no record points to a decommissioned old machine.

Failing signals: Only www is configured; root domain resolves to an old IP; AAAA record points to a machine without IPv6 support.

5. The root domain and www ultimately resolve to the same canonical URL.

Pass criteria: One URL 301 redirects to the other; both with and without trailing slash resolve to the same address; no duplicate content where both addresses return 200.

Fail signals: Both return 200; redirect chain exceeds one hop; redirect target is a 404.

6. TTL and change windows are documented.

Pass criteria: TTL for critical records is known; there is a plan to lower TTL before changing IPs; rollback IPs and old records are archived.

Fail signals: TTL is unknown; records changed on the day of the server switch; old server already shut down.

III. HTTPS

7. Certificate covers both the main domain and www, chain is complete, with expiry reminders.

Pass criteria: Neither address shows a certificate warning; certificate chain is complete; renewal reminder set before expiry; HTTP 301 redirects to HTTPS.

Fail signals: Only one domain covered; certificate chain missing intermediate cert; no one monitors the expiry date; page still loads http:// resources.

IV. Email & Domain Authentication

8. If sending/receiving email, MX, SPF, DKIM, and DMARC are all configured.

Pass criteria: Can send and receive; SPF, DKIM, and DMARC pass in test headers; only one SPF record; DMARC starts in monitor mode before tightening.

Fail signals: MX present but no SPF; multiple SPF records listed side by side; DKIM not configured; DMARC set to reject all from the start.

V. Launch & Operations

9. Old addresses have 301 redirects, no 404s left behind.

Pass criteria: Old domain, old paths, and old section URLs all redirect to new addresses; redirect targets return 200; redirect chain does not exceed one hop.

Fail signals: Old domain DNS simply removed; old articles return 404; redirects point to another redirect address.

10. DNS resolution and availability monitoring in place, with anomaly notifications to responsible parties.

Pass criteria: At least one external monitoring check covers domain resolution and homepage status; alerts reach the on-call person; there are change records.

Red flags: Issues are only discovered through customer feedback; monitoring notifications go to a group nobody checks; no rollback records exist.

Order on Launch Day

Check items 3, 4, and 5 first to confirm traffic reaches the new server; then check item 7 to confirm HTTPS is intact; finally check items 9 and 10 to confirm the old addresses and monitoring are connected.

Email changes can be done a day ahead—don't stack them in the same hour as the site cutover.

Related Reading: