Domain, DNS and HTTPS Verification for a New Site
Key takeawayDomain and certificate issues sit at the lowest layer and surface as unreachable pages, odd redirects or regional failures that are expensive to diagnose. This sheet clears DNS, certificate, redirect and mixed content problems before launch.
Industries and use cases
- Binding a new domain to a server for the first time
- After changing server, CDN or certificate provider
- When users report the site is unreachable in some regions
- While migrating from HTTP to HTTPS
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| A record | The apex A record points to the current server or CDN IP with no stale records left | High | Delete old IPs and keep one live record so traffic cannot land on a retired server. |
| www and apex | Both resolve and one 301s to the other with no parallel pair | High | Fix the preferred host in server config and permanently redirect the other. |
| CNAME and NS | With a CDN the CNAME points to the hostname given by the provider, and NS matches the registrar | Medium | Allow propagation after changing NS and avoid repeated edits. |
| TTL | TTL is lowered to 300 seconds 24 hours before the switch and restored afterwards | Medium | A low TTL allows fast rollback; restore the normal value once stable. |
| Certificate coverage | The certificate includes apex and www, and multi-domain certificates list every bound domain | High | A missing www entry triggers warnings for part of your traffic, so tick both at issue time. |
| Chain and validity | The chain is complete, more than 60 days remain and expiry alerts are configured | High | Enable auto-renewal and add a manual reminder 30 days before expiry as a fallback. |
| Forced HTTPS | HTTP 301s to HTTPS exactly once with no loop | Medium | Redirect at one layer only; duplicate rules in the app and the CDN cause loops. |
| Mixed content | No HTTP images, scripts or fonts are requested from HTTPS pages | High | Filter console warnings for mixed content and switch assets to HTTPS or protocol-relative URLs. |
| HSTS | HSTS is enabled only after every subdomain supports HTTPS | Medium | Start with a short max-age, confirm no legacy subsystem is missed, then extend. |
| Security headers | Basic headers such as X-Content-Type-Options and Referrer-Policy are set | Low | Inject them centrally at server or CDN level to avoid per-page gaps. |
| Common subdomains | Resolution and certificate status of m, blog and static subdomains are confirmed | Medium | Subdomains are easily forgotten; open each one and check for certificate errors and 404s. |
| Speed baseline | Time to first byte under 800ms with no timeouts in multi-region tests | Medium | Compare direct origin and CDN responses to see whether origin or routing is the bottleneck. |
Common misjudgements
- Editing records repeatedly while propagation is slow: old and new records coexisting before the TTL expires is normal, and frequent edits make it worse.
- Testing only the apex: roughly half of visitors type www, and certificate or redirect problems often appear only there.
- Assuming the padlock means HTTPS is healthy: mixed content and chain problems stay silent in some browsers.
How to use this checklist
- Use with the full launch sheet; this is the expanded domain and certificate section of it.
- Re-run immediately after changing provider, renewing a certificate or adjusting the CDN.
- Log DNS records and certificate expiry in a calendar and act one month ahead.
FAQ
How long does DNS take to propagate?
Usually within the TTL, commonly 10 minutes to 24 hours depending on record settings.
Can a free certificate be used on a production site?
Yes, provided auto-renewal is reliable and it covers both apex and www.
Should www or the bare domain be the primary address?
Either works; the key is fixing one and permanently redirecting the other instead of running both.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
Full Launch Checklist for a New B2B WebsiteBrand Entity Review for AI Overviews and Answer EnginesRich Results Testing Workflow Before Site ReleaseFinal Pre-Publish Review for Content Used as an AI Sourcehreflang Configuration Review for Multilingual SitesNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.