Domain health checks that catch expiring domains and broken HTTPS before visitors do
Your website depends on more than the page visitors see. A missed domain renewal can interrupt it, and an HTTPS page can still refer to files over HTTP.
# DNSyoursite.com. A 203.0.113.24www.yoursite.com. CNAME yoursite.com.shop.yoursite.com. CNAME shops.example-host.net.A subdomain points to a service that's gone# Registrationexpiration 2026-12-01Your domain name expires soon or has expired# Home pagestrict-transport-security: max-age=300Always-use-HTTPS setting (HSTS) is missing or weak<img src="http://yoursite.com/hero.jpg">Secure pages load some files without HTTPSSiteCMD's free scan reads your domain's public records and your home page's markup. Hosted scans also check that HTTP redirects to HTTPS, that www and non-www reach one address, and your SSL certificate.
What a scan can flag, and what's up to you
A scan can flag
- Your domain's public recordsThe free scan reads them, along with your home page's markup.
- Redirects and your SSL certificateHosted scans check that HTTP redirects to HTTPS, that www and non-www reach one address, and your certificate.
Up to you
- Renewing your domainYour registration and your certificate run on separate dates, so renew the registration with your registrar.
- DNS propagationThe scan doesn't compare answers from locations around the world.
Explore domain health and HTTPS setup
Fix mixed content and set up your HTTPS and www redirects
4 guides
Replace insecure file and form addresses that remain on an HTTPS page.
How to fix
- Locate the requestOpen the browser console on the affected page and find the resource named in the mixed content warning.
- Replace the insecure referenceConfirm the resource works over HTTPS, update the address where the page gets it, then reload and check for remaining warnings.
Domain and HTTPS
Secure pages load some files without HTTPS
A secure page is still pulling in some images, scripts, or styles over plain http, weakening the encryption visitors expect.
Fix with your agent
# SiteCMD Fix Brief: Secure pages load some files without HTTPS Site: https://yoursite.com ## What is wrong A secure page is still pulling in some images, scripts, or styles over plain http, weakening the encryption visitors expect. ## How to fix Reproduce the affected route with browser Network and Console tools to confirm each observed HTTP resource is actually requested. For each one, verify the same asset works over HTTPS before updating the authoritative template, stylesheet, CMS field, or configuration; if the origin is HTTP-only, self-host or replace it, and swap localhost or loopback references for the intended deployed endpoint. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Send HTTP requests to their HTTPS destination and avoid conflicting redirect rules.
How to fix
- Make sure your site has a valid certificate, which lets it load over https, for every address it uses, such as with and without www.
- In your host's or CDN's settings, turn on the option that sends visitors from http:// to https://, which may be called Force HTTPS or Always use HTTPS.
- If you can't find it, set up a permanent redirect from http to https.
- Then run the check again.
Domain and HTTPS
Your site still opens without HTTPS
Your site still answers over plain http://, so visitors can land on an unencrypted page.
Fix with your agent
# SiteCMD Fix Brief: Your site still opens without HTTPS Site: https://yoursite.com ## What is wrong Your site still answers over plain http://, so visitors can land on an unencrypted page. ## How to fix Terminate TLS with a valid certificate for every public hostname, then redirect the HTTP listener to the canonical HTTPS origin with a 301 or 308 and no chain through alternate hosts. Build the redirect from configured canonical hosts, never from an untrusted Host header, and verify alternate hostnames, IPv6, query and encoded paths, and any allowed non-GET requests before adding HSTS. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Choose www or non-www and keep redirects, canonical tags and certificates in step.
How to fix
- Name the preferred page addressSet canonical tags to the chosen host and use that host in internal links.
- Keep the redirect on the other hostSend each alternate-host URL to its matching page on the preferred host, rather than sending every request to the home page.
Domain and HTTPS
Site loads at both www and non-www addresses
Both the www and plain versions of your domain serve content on their own instead of one leading to the other.
Fix with your agent
# SiteCMD Fix Brief: Site loads at both www and non-www addresses Site: https://yoursite.com ## What is wrong Both the www and plain versions of your domain serve content on their own instead of one leading to the other. ## How to fix Serving both hosts can be intentional, but duplicate public content needs one coherent strategy: pick the public host from the site's existing links, certificates, cookies, and search configuration, then redirect the alternate known hostname at the edge or web server to that fixed destination, preserving path and query. Never build the destination from an unvalidated `Host` header. Request both hosts over HTTP and HTTPS to confirm a single hop, correct 301/308 semantics, and certificate coverage. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Understand how browsers remember HTTPS before extending that rule to every subdomain.
How to fix
- First make sure every part of your site, including any subdomains, opens over https without errors.
- If your host or CDN has a setting for HSTS, which tells browsers to always use https for your site, turn it on; otherwise add it.
- Start with a short duration and raise it bit by bit while nothing breaks, and leave the options for subdomains and preloading off unless you've checked every subdomain, since they are hard to undo.
- Once the duration reaches a year, run the check again, since it keeps flagging anything shorter.
Domain and HTTPS
Always-use-HTTPS setting (HSTS) is missing or weak
Your site's always-use-HTTPS setting is missing, too short or broken, so browsers may not keep using secure connections.
Fix with your agent
# SiteCMD Fix Brief: Always-use-HTTPS setting (HSTS) is missing or weak Site: https://yoursite.com ## What is wrong Your site's always-use-HTTPS setting is missing, too short or broken, so browsers may not keep using secure connections. ## How to fix Confirm every host, route, and certificate works over HTTPS, then enable `Strict-Transport-Security` at one authoritative layer with a short `max-age` (for example 300) and raise it gradually as monitoring stays clean. Treat `includeSubDomains` and preload as separate, hard-to-reverse decisions that need a full subdomain inventory first. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Renew your domain and set up DNSSEC and CAA records
3 guides
Review the registration date and renewal settings before your domain runs out.
How to fix
- Review the renewal paymentConfirm auto-renewal is enabled if you want it, and replace an expired or canceled payment card in the registrar account.
- Keep renewal notices reachableUpdate an old contact email and check the registrar's renewal reminders before the registration ends.
Domain and HTTPS
Your domain name expires soon or has expired
Your domain's registration is approaching or past its expiration date, which risks losing the domain and everything on it.
Fix with your agent
# SiteCMD Fix Brief: Your domain name expires soon or has expired Site: https://yoursite.com ## What is wrong Your domain's registration is approaching or past its expiration date, which risks losing the domain and everything on it. ## How to fix Read the reported RDAP expiration date and urgency tier first; a date within 90 days is a planning warning, not proof that auto-renew failed, and even a past date needs confirmation because renewal publication can lag. Confirm status and renewal intent in the authoritative registrar account, renew immediately if needed, verify auto-renew and the payment path, and keep registrar access recoverable independently of the domain being protected. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Learn what DNSSEC protects and whether to turn it on for your domain.
How to fix
- Start signing at the DNS providerConfirm the DNS host and registrar support the setup, then enable signing and get the DS values the DNS provider supplies.
- Publish the matching DS recordAdd those values through the registrar, then test the whole chain with a tool such as DNSViz.
Domain and HTTPS
Your DNS records aren't signed (DNSSEC)
Your domain's DNS responses are not cryptographically signed, so they could in theory be forged in transit.
Fix with your agent
# SiteCMD Fix Brief: Your DNS records aren't signed (DNSSEC) Site: https://yoursite.com ## What is wrong Your domain's DNS responses are not cryptographically signed, so they could in theory be forged in transit. ## How to fix DNSSEC is optional hardening most sites skip; treat it as a nice-to-have, not an emergency. Enable signing at your DNS host first, add the resulting DS record at your registrar to link the zone into the chain of trust, then verify with `dig +dnssec` or an online DNSSEC analyzer. Plan any later DNS-provider migration as a documented key/DS rollover so the zone never fails validation. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Limit certificate issuance to the authorities your hosting setup needs.
How to fix
- Find out which certificate authorities, the companies that issue your https certificates, your site uses, including any your host or CDN uses for you.
- In your DNS settings, add one CAA record, which names a company allowed to issue your certificates, for each of them, using the value each one documents, such as letsencrypt.org for Let's Encrypt.
- Make sure you include every one your setup may use, because leaving one out can make a later certificate renewal fail.
- Then run the check again.
Domain and HTTPS
Nothing limits who can issue your certificates (CAA)
Nothing on your domain restricts which certificate authorities may issue certificates for it, widening who could impersonate you.
Fix with your agent
# SiteCMD Fix Brief: Nothing limits who can issue your certificates (CAA) Site: https://yoursite.com ## What is wrong Nothing on your domain restricts which certificate authorities may issue certificates for it, widening who could impersonate you. ## How to fix Identify every certificate authority that actually issues for the domain, including host- or CDN-managed certificates, then publish one `CAA 0 issue` record per allowed CA at the apex, with `issuewild` handling if you use wildcards. Include every CA your certificate automation may use before rollout; CAA is an issuance-time request to compliant public CAs, and omitting a required issuer can make a later renewal fail. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Find forgotten subdomains someone else could take over
1 guide
Clean up DNS names that still point to a service you no longer control.
How to fix
- Remove or replace the record before retiring the resourcePoint the name elsewhere or delete its record before you release the old service, so the name never points at a resource someone else could claim.
- Review the other names attached to the same accountLook for forgotten preview sites, support pages and campaign addresses. Keep each active name attached to a resource you control, and remove records for names you've retired.
Domain and HTTPS
A subdomain points to a service that's gone
A subdomain points to a third-party service that is no longer set up there, and someone else could claim it and take over.
Fix with your agent
# SiteCMD Fix Brief: A subdomain points to a service that's gone Site: https://yoursite.com ## What is wrong A subdomain points to a third-party service that is no longer set up there, and someone else could claim it and take over. ## How to fix Confirm the chain with `dig` first; an empty address result confirms the availability problem but not that another account can claim the target. If www is no longer used, delete the CNAME record; if it should work, re-point it at the current live hostname, and for shared-platform targets use the provider's own domain-claim documentation to determine whether the identifier is claimable before labeling it a takeover. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Frequently asked questions
Can I use SiteCMD's domain health check as a DNS checker?
Not for propagation. The free scan reads selected public DNS records for your domain; it doesn't compare answers from locations around the world.
Does my domain renew when my SSL certificate renews?
No. Your domain registration and your SSL certificate run on separate dates. Renew the registration with your registrar, even if your host renews the certificate for you.