Confirm control and administrative ownership

Verify that the domain sits in the correct registrar account and that the organization—not an employee, freelancer, or agency—is the documented account holder where appropriate. Confirm access to the registrant email, recovery methods, billing profile, and authorization controls.

Record the registrar, account owner, renewal date, payment owner, and internal contact in a secure inventory. Avoid placing passwords or recovery codes in the inventory itself.

Review history and brand fit

Run an age lookup and inspect archived versions of the site. Search for previous brand names, unrelated topics, spam, or confusing associations. Check relevant trademark databases and business-name requirements for the markets you intend to serve. When the legal risk is meaningful, get qualified advice.

An old registration is not a substitute for this review. Use the domain history research process to separate verified facts from assumptions.

Secure the registration

Enable multi-factor authentication, transfer lock, and account-change notifications. Verify that renewal is configured as intended and that the payment method will remain valid. Protect the associated email account and store recovery codes safely.

For high-value domains, consider registry-lock or enhanced protection services when supported and justified by the risk.

Validate DNS and web delivery

Before launch:

  1. Document existing DNS records and lower TTLs only when a planned migration requires it.
  2. Configure the new web and email records using provider instructions.
  3. Test the apex domain and www behavior over HTTPS.
  4. Confirm redirects preserve useful paths and do not create loops.
  5. Enable DNSSEC only when the registrar, DNS provider, and operational team can manage it correctly.

The domain status and DNS guide explains why registry statuses, nameservers, and DNSSEC answer different questions.

Test email and search essentials

Configure SPF, DKIM, and DMARC with your email provider and test both sending and receiving. Publish a useful error page, robots file, and sitemap where appropriate. Verify analytics and search-console ownership through accounts the organization controls.

Create a handover record

Document providers, responsible people, renewal procedures, DNS architecture, and emergency contacts. Schedule periodic access and renewal reviews. The best launch checklist remains useful after launch because it gives the next maintainer a trustworthy starting point.

Free domain age checkerBulk domain age checker