What this checker looks at
The domain’s address records (A and AAAA), its name servers and whether they answer, its DNSSEC signatures as validating resolvers see them, and its CAA records.
Free tool
What the world sees for your domain.
The records public DNS holds for the name, how many seconds each copy is still kept, and the DNSSEC chain link by link – so a broken signature is told apart from one that was never set up.
Read from your browser through Cloudflare’s and Google’s public resolvers, which validate DNSSEC. A broken chain is confirmed by asking again with validation switched off.
Your browser asks 22 public DNS resolvers the same question at once, and places on every continent look it up through their own local DNS – each one’s answer, how long it keeps that answer and whether they agree. Nothing goes through Xovris.
Asked from your browser over DNS over HTTPS. These 22 resolvers are the ones that answer other sites’ pages directly, measured on 2026-10-02; one that stops answering is shown as exactly that, never guessed. The places around the world are Globalping, a free and open network of probes run by jsDelivr: one place on each continent asks the address you typed, once, and nothing else is sent.
HTTPS, the certificate, DNS, mail and registration – the whole address in one run.
Runs in your browser – nothing is saved to an account.
What each part of the answer means, and what to do when one is not right.
Enter a domain to see what visitors’ browsers get from the internet’s public address book (DNS): the addresses it points to, the name servers that answer for it and whether its DNSSEC signatures validate.
The domain’s address records (A and AAAA), its name servers and whether they answer, its DNSSEC signatures as validating resolvers see them, and its CAA records.
No address records means browsers find nothing at that name. Name servers that do not answer, or a domain missing from DNS, take everything on the domain offline, email included. Broken DNSSEC makes validating resolvers refuse to answer, so most visitors fail to reach the site.
Connect your DNS provider and Xovris writes the change the check’s finding names - a missing or changed record set to the value it last verified - within your policy, and proves it with the same check. Prefer to do it yourself instead? Restore the missing record at your DNS provider, point the domain at name servers that answer, or repair DNSSEC by updating or removing the DS record at your registrar. A change can take up to the record’s TTL to reach everyone.
Straight answers, from what the check itself does.
Read the guide: Website down? How to tell if it is DNSXovris checks your DNS every 3 minutes. On Personal it puts a broken record back from its last verified version and proves the fix.
The answer on this page is xovris.ai’s own, recorded by this check 18 November at 23:05 UTC. Nothing here is a sample: name your own address and Xovris runs it for you.
Each technical word this page uses, said simply.