Domain, DNS, SSL, and Business Email Setup Checklist for a New Website

Overview

A domain is the address visitors type into a browser. Hosting is the service that stores and delivers the website. DNS connects the domain to the right services, SSL encrypts browser connections, and business email uses the domain for professional addresses such as hello@example.com.

These systems are related but managed separately in many setups. Your domain may be registered with one company, hosted with another, and connected to an email provider elsewhere. Before changing anything, create a simple record of the services involved, the account owners, and the current DNS settings. This reduces the risk of deleting a record that supports email or another important service.

If you are still choosing a platform, compare the practical details rather than focusing only on the advertised plan. The guide to choosing web hosting for a small business covers factors such as support, backups, scalability, and included features.

Use this basic order of operations:

1. Confirm the domain and hosting accounts.
2. Choose whether DNS will be managed at the registrar, host, or another DNS provider.
3. Connect the domain using nameservers or individual DNS records.
4. Configure email records without disturbing existing services.
5. Enable SSL and confirm both secure and non-secure versions of the site behave correctly.
6. Test the website, email, redirects, forms, and administrative access.

Checklist by scenario

Scenario 1: A new domain and a new website

• Record the exact domain spelling, including the preferred version with or without www.
• Confirm that the domain registration is active and that you can access the registrar account.
• Publish the website on its hosting platform before changing public DNS, if the platform allows a temporary preview address.
• Find the host’s connection instructions. These may ask you to replace nameservers or add an A, AAAA, or CNAME record.
• Set the root domain and www version according to the host’s instructions. Do not guess record values.
• Set the preferred domain in the website platform and configure a redirect from the other version.
• Enable the host’s SSL option or add the certificate supplied by your platform. Wait for certificate validation before testing.
• Create business email accounts only after confirming which provider will handle mail.

Scenario 2: An existing domain is moving to new hosting

• Export or document the current DNS zone before making changes.
• Identify every existing record, especially MX, TXT, verification, subdomain, and third-party service records.
• Build and test the website on the new host before changing the live connection where possible.
• Copy required DNS records to the new DNS provider if you are changing nameservers. Changing nameservers without copying records can interrupt email and connected services.
• Lowering a record’s TTL in advance may help with planning, but it does not guarantee an immediate change everywhere.
• Change the relevant records or nameservers during a period when you can monitor the site and email.
• Keep the previous hosting account available until the new website and email have been checked.

For a fuller migration workflow, see how to migrate a website to new hosting without downtime. A migration should also include a current backup and a tested restore path; the website backup and restore guide provides a useful companion checklist.

Scenario 3: Adding business email to an existing website

• Decide whether email will be provided by the web host, a dedicated email service, or another business platform.
• Obtain the provider’s exact MX records and any required TXT records.
• Remove obsolete MX records only after confirming that they no longer support active mailboxes.
• Add sender-authentication records such as SPF, DKIM, and DMARC when the provider supplies them. Follow the provider’s syntax and avoid creating multiple competing SPF records.
• Create the mailbox, recovery method, display name, signature, and forwarding rules.
• Send test messages to and from an external address. Check delivery, replies, attachments, spam placement, and mobile access.
• Document who controls the email account and where renewal or security notices are sent.

Scenario 4: Using a one-click website launch

A one-click launch can simplify hosting and builder setup, but it does not remove the need to review DNS. Confirm whether the launch process changes nameservers, adds records, or asks you to verify ownership with a TXT record. Check the final domain, SSL status, email routing, contact forms, and any subdomains before treating the launch as complete.

What to double-check

Use this verification pass after DNS changes have had time to become visible in the locations and networks you use:

• Domain: The spelling, renewal status, registrant contact, and account recovery details are correct.
• DNS: The root domain and www resolve to the intended website. Unused or conflicting records are removed only when their purpose is known.
• Email: MX records point to the intended provider, and the required SPF, DKIM, and DMARC records are present and correctly formatted.
• SSL: The certificate covers the domain visitors use. The site loads over HTTPS, and HTTP requests redirect appropriately if that is the chosen configuration.
• Website: Navigation, images, forms, downloads, analytics, and embedded services work on desktop and mobile.
• Security: Registrar and hosting accounts use strong, unique passwords and multi-factor authentication where available.
• Recovery: Backups exist, restoration instructions are available, and at least one person knows how to regain access.

For SSL-specific decisions, consult SSL certificates explained. The broader website security checklist can help turn this launch review into an ongoing maintenance routine.

Common mistakes

• Changing nameservers without copying records: This can affect email, verification services, subdomains, and integrations.
• Adding the wrong record type: A host may require a CNAME for www but an A record for the root domain. Use the provider’s instructions exactly.
• Publishing multiple SPF records: SPF is generally combined into one TXT record rather than added as separate competing policies.
• Testing only one domain version: Check the root domain, www, HTTPS, and any planned subdomains.
• Assuming DNS changes are instant: Visibility can differ by resolver and network. Use an external DNS checker and test from more than one connection. See how to check DNS propagation status.
• Deleting the old host too soon: Keep the previous site and backups until the replacement is verified.
• Ignoring forms and email delivery: A website can appear correct while contact submissions fail or messages go to spam. Test the complete path.

When to revisit

Save this checklist with your website records and use it before seasonal planning cycles, a rebrand, a hosting change, or the launch of a new service. Revisit it whenever a domain registrar, DNS provider, hosting platform, email provider, or website builder changes. It is also worth reviewing after staff turnover, a security incident, a failed renewal, or the addition of a new subdomain or third-party integration.

Before making a change, take a current DNS export or screenshot, confirm account access, and identify the person responsible for rollback. After the change, test from a normal browser, a private window, a mobile connection, and an external email account. Record the date, the change made, and the result.

The practical finish line is not simply that the homepage loads. A successful launch means visitors reach the intended secure address, customers can use the site’s forms, staff can send and receive business email, and the team can restore the website if something goes wrong. Keep the checklist updated as your tools and workflows change, and it will remain useful for the next launch as well as the current one.