LEYUN · SITE LAUNCH CHECKLIST独立站上线自查清单库

Domain, DNS and HTTPS Verification for a New Site

Sections: Pre-launch Checks · Reviewed: 2026-11-21 · 12 items

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

Checklist: domain, DNS and HTTPS verification
Check itemPass criteriaRisk levelFix hint
A recordThe apex A record points to the current server or CDN IP with no stale records leftHighDelete old IPs and keep one live record so traffic cannot land on a retired server.
www and apexBoth resolve and one 301s to the other with no parallel pairHighFix the preferred host in server config and permanently redirect the other.
CNAME and NSWith a CDN the CNAME points to the hostname given by the provider, and NS matches the registrarMediumAllow propagation after changing NS and avoid repeated edits.
TTLTTL is lowered to 300 seconds 24 hours before the switch and restored afterwardsMediumA low TTL allows fast rollback; restore the normal value once stable.
Certificate coverageThe certificate includes apex and www, and multi-domain certificates list every bound domainHighA missing www entry triggers warnings for part of your traffic, so tick both at issue time.
Chain and validityThe chain is complete, more than 60 days remain and expiry alerts are configuredHighEnable auto-renewal and add a manual reminder 30 days before expiry as a fallback.
Forced HTTPSHTTP 301s to HTTPS exactly once with no loopMediumRedirect at one layer only; duplicate rules in the app and the CDN cause loops.
Mixed contentNo HTTP images, scripts or fonts are requested from HTTPS pagesHighFilter console warnings for mixed content and switch assets to HTTPS or protocol-relative URLs.
HSTSHSTS is enabled only after every subdomain supports HTTPSMediumStart with a short max-age, confirm no legacy subsystem is missed, then extend.
Security headersBasic headers such as X-Content-Type-Options and Referrer-Policy are setLowInject them centrally at server or CDN level to avoid per-page gaps.
Common subdomainsResolution and certificate status of m, blog and static subdomains are confirmedMediumSubdomains are easily forgotten; open each one and check for certificate errors and 404s.
Speed baselineTime to first byte under 800ms with no timeouts in multi-region testsMediumCompare 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.

Note: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.