Free tool · no signup

Is your custom domain actually set up right?

We taught computers to write software — and still make a human copy-paste DNS records by hand. Paste a domain and see, in seconds, exactly what your users see when it breaks: DNS, CNAME and apex, HTTPS, the SSL certificate, and the http-to-https redirect.

Try one:

Read-only checks over public DNS and TLS. Nothing is stored.

Your result

Copied

Every check above is a step someone sets up by hand, and re-checks when it breaks. Custom Domain does all of it automatically, so your users never touch a DNS panel.

What it checks

The six things that decide whether a custom domain actually works for your users — the same things that silently break onboarding.

DNS resolution

Whether the domain points anywhere at all, and where.

CNAME and apex

A CNAME on a root domain is invalid — a classic silent failure. We catch it.

HTTPS reachable

Whether TLS actually answers on port 443, or the site just hangs.

SSL certificate valid

Expired, not-yet-valid, or issued for the wrong name — the browser-warning cases.

Renewal runway

How many days until the certificate expires — before it fails at 3am.

HTTP to HTTPS redirect

Whether plain http:// sends users to the secure version, or leaves them on it.