Skip to main content

Product Launch Domain Checklist: Name to Go-Live

Published 2026-10-02 · Updated 2026-11-04 · By

Startups Checklist

Launch week is the wrong time to discover the domain has a problem: the name clashes with a trademark, the email lands in spam, or the registration lapses because the card on file expired. This product launch domain checklist breaks the work into four stages, from working title to launch day, with the order that saves the most trouble.

Stage 1: Settle the name (6 to 8 weeks out)

  • Write down your working title and two backups. A launch rarely survives on one candidate.
  • Check all three on the extensions you'd accept. A TLD Sweep shows .com, .io, .app and others for up to 10 names at once.
  • Search for the name in your market. Look for businesses, apps and products with the same or a similar name.
  • Run a trademark search in the countries where you'll sell. A domain being open doesn't mean the name is free to use.
  • Say it to five people who haven't heard it and ask them to spell it back.

Stage 2: Register (4 to 6 weeks out)

  • Register the main domain as soon as the name is chosen. Waiting invites someone else to take it.
  • Register the obvious neighbours if they're affordable: the .com if you launch elsewhere, and the plural or a common misspelling. The domain typo generator shows which misspellings people are likely to make.
  • Use a company email address as the registrant contact, not a personal one that might leave with an employee.
  • Turn on auto-renew and check the payment card won't expire before the renewal date.
  • Grab the matching social handles the same day.

Stage 3: Secure and configure (2 to 4 weeks out)

  • Turn on registrar lock so the domain can't be transferred without your approval.
  • Turn on two-factor login at the registrar.
  • Enable privacy protection for the registrant contact, where your registrar offers it.
  • Set up DNS for the website and any subdomains you'll need, such as app, help or status.
  • Set up email authentication: SPF, DKIM and DMARC records. Without them, launch emails are more likely to land in spam.
  • Install an HTTPS certificate and test that every version of the address redirects to one canonical URL.

Stage 4: The final week on the product launch domain checklist

  • Send test emails to Gmail, Outlook and a work address, and check they arrive in the inbox.
  • Load the site from a phone on mobile data, not just the office network.
  • Check the redirects from your extra domains.
  • Write down where everything is: registrar, DNS host, email provider, certificate renewal. Share it with at least one other person on the team.

A worked example

A small team (invented for this example) is launching a budgeting app. Six weeks out, their working title turns out to match a registered trademark in a neighbouring category, so they switch to their first backup. They register it on .com and .app, plus the plural. Three weeks out they set up SPF, DKIM and DMARC and discover their newsletter tool needed its own DKIM record. They'd have found that out on launch day otherwise. In the final week, test emails to three providers all reach the inbox, and the launch goes out on time.

Common mistakes

Registering under a personal account. If that person leaves, the domain can go with them.

Skipping email authentication. Launch announcements from a new domain are especially likely to be filtered.

Assuming auto-renew will just work. Expired cards are one of the most common reasons domains lapse.

For the checks to run before buying any domain, see the domain name checklist before registering.

Related reading

Frequently asked questions

How early should I register my launch domain?

As soon as the name is chosen, ideally four to six weeks before launch. That leaves time for DNS, email and security set-up.

Do I need to register misspellings?

Not all of them. Register the most likely one or two if they're cheap, and redirect them to the main site.

← Back to Blog