Understand the setup
Find out who controls the domain, DNS, website and email, especially when taking over an existing setup.
Domain checklist
A practical order to work through domain ownership, DNS, website routing and email authentication. If you are inheriting a business domain, changing providers or fixing deliverability, start here.
Start with your problem
A website, its domain and its email can use different providers. Start with the relevant guide before changing settings.
Find out who controls the domain, DNS, website and email, especially when taking over an existing setup.
Record the current settings, plan the cutover and check the website and email after the change.
Separate mail that bounces or lands in spam from sign-in, mailbox and Microsoft 365 administration problems.
Use the recovery guides when you suspect someone has accessed a mailbox or changed its settings.
Expand the detailed checks when you are ready to map the services, plan a handover or verify provider settings.
For the wider release, use the website launch checklist. For a plain-language explanation, see the domains and hosting questions.
Ownership map
A domain problem is rarely just one thing. The domain may be registered with one provider, DNS hosted somewhere else, the website served by a third company and email delivered through Microsoft 365, Google Workspace or another mail platform.
Confirm the registrar, renewal date, account owner, contact email and nameserver settings. This is the control point that decides where DNS is hosted.
Export the current zone before changes. Record A, CNAME, MX, TXT, SPF, DKIM, DMARC, autodiscover and verification records so rollback is realistic.
Check the canonical hostname, redirects, SSL certificate, hosting account, CDN or proxy layer and form delivery path before moving a website.
List every service that sends as the domain: Microsoft 365, website forms, invoice software, booking systems, CRM tools and marketing platforms.
Use the path
Start with ownership and control, not necessarily the first symptom. Confirm who controls the domain registration and DNS zone. Then record the current website host, mail provider, transactional senders and any third-party systems that send as the domain. Only after that should you change records.
Export the zone, screenshot the registrar nameservers, record the current TTLs and write down the rollback record values.
List every sender that uses the domain, including Microsoft 365, website forms, invoices, booking tools, CRMs and bulk mail platforms.
Confirm the canonical domain, SSL certificate, redirect rules, analytics access, form delivery, backups and who can update DNS quickly.
Check the live website, contact forms, SPF/DKIM/DMARC alignment, mail delivery, Search Console coverage and any provider warning banners.
Handover sequence
For a domain handover, record the ownership, DNS host, mail platform and website host before changing any TXT, MX, A or CNAME record. If those facts are missing, the first task is discovery, not migration.
Confirm who the domain is registered to, who can authorise registrar changes and whether billing or recovery details still belong to the business.
Record the nameservers at the registrar and the dashboard that controls the live DNS zone. Editing the wrong DNS dashboard is a common handover failure.
Document current TTLs and planned timing. Lowering TTLs before a planned move can make rollback faster, but nameserver and resolver caching still need patience.
Name the person who can reverse the change, the old record values and the cutover window where someone will watch website, form and mail behaviour.
Related support
These pages are the next step when the checklist identifies a real routing or provider problem. They focus on practical diagnostics and clear handover notes rather than vague SEO theory.
Search and launch impact
Domain, DNS and email work can spill into search visibility when it changes redirects, canonicals, sitemap URLs, contact-form delivery, analytics, verification records or Search Console ownership. Treat those as launch and technical SEO checks, not just DNS edits.
Use this when DNS or hosting changes affect crawl access, robots rules, canonicals, redirects, sitemap entries or structured data.
Use this when Search Console evidence, indexing state, page intent, metadata or internal links need careful review and correction.
Use this guide when domain work overlaps with launch checks, measurement, project-page review or search visibility.
Use the launch checklist tool to capture canonical URLs, forms, analytics, sitemap, backups and handover notes after a DNS change.
Use the maintenance calendar when DNS, mail authentication, backups, profile accuracy and sitemap checks need regular review.
Use the tools and checklists page before changing records, launch settings or public profile details.
Reference checks
SPF, DKIM, DMARC and sitemap/canonical changes can look like tiny text edits, but they affect trust, mail delivery and crawl signals. Use the checklist article for the practical workflow, then verify the final records against the active provider's own documentation before publishing changes.
Use InternetNZ context when the handover involves a `.nz` domain, registrar relationship or domain-holder responsibility.
Use provider TTL documentation when planning propagation, cache behaviour and rollback timing around DNS changes.
Check Google's SPF/DKIM/DMARC guidance when Gmail or Google Workspace is part of the sending path.
Use Microsoft's DMARC guidance when the domain sends through Microsoft 365 or Defender-managed mail flows.
Use Microsoft's DNS-record setup guidance when connecting a domain to Microsoft 365 and adding provider-specific records.
Use Search Central guidance when sitemap, canonical or recrawl decisions are part of a website handover.
Keep the official links beside the DNS export and change note so the next person can verify why each record exists.
Help with your next step
Tell me what is changing and which services need to keep working. I can help check the setup, plan the change and document the handover.