Domains and security

How to validate a domain before launch

A launch workflow for confirming DNS records, domain ownership signals, SSL coverage, and security headers on the public endpoint.

A domain can look ready in one dashboard while still failing from the public internet. DNS caches, certificate chains, CDN settings, and headers all need separate checks.

Validate the public hostname, not only the origin server or provider preview URL.

Confirm DNS resolution

Check A, AAAA, CNAME, NS, SOA, MX, TXT, and CAA records depending on what the domain is used for.

For CDN or SaaS setups, verify both apex and www hostnames and make sure old records are not still active.

Inspect certificate coverage

The SSL certificate should cover the exact hostname users visit, including subdomains and wildcard assumptions.

Check issuer, validity dates, chain completeness, and days remaining after DNS or load balancer changes.

Review public security headers

Security headers may be set by the app, proxy, CDN, or hosting platform. Check the final public response.

Pay special attention to HSTS, CSP, framing controls, referrer policy, and permissions policy.

Domain launch checklist

  • Check DNS records for apex, www, and important subdomains.
  • Verify WHOIS or registrar details when ownership or nameservers look wrong.
  • Confirm SSL SAN coverage, issuer, chain, and expiration.
  • Check security headers on the final public URL.
  • Repeat checks after DNS, CDN, proxy, or load balancer changes.

Related guides

Learn the workflow behind this tool and what to check next.

Related tools