What this checker looks at
The record you choose – A, AAAA, CNAME, MX, TXT or NS – as 22 public resolvers answer it, with each one’s remaining TTL and response time, grouped by answer so a change still on its way shows at a glance.
Free tool
Has your change reached everyone yet?
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.
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.
What each part of the answer means, and what to do when one is not right.
Changed a record? Enter the name and see what 22 public resolvers answer right now, how long each keeps its answer and whether they all agree.
The record you choose – A, AAAA, CNAME, MX, TXT or NS – as 22 public resolvers answer it, with each one’s remaining TTL and response time, grouped by answer so a change still on its way shows at a glance.
Resolvers keep an answer for its TTL, so until that runs out some still hand out the old value. The longest TTL among the old answers is the most you will wait. A resolver that filters harmful sites may also answer differently on purpose.
A day before a planned change, lower the record’s TTL to 300 seconds, make the change, and once every resolver agrees raise the TTL again. A wrong answer that outlives its TTL usually means the record was changed at a DNS provider your domain no longer uses.
Straight answers, from what the check itself does.
Read the guide: Website down? How to tell if it is DNSXovris checks your records every 3 minutes and tells you the moment one changes – and, on Personal, when a change breaks something it follows the fault to its cause, puts that right and proves it works again.
The answer on this page is xovris.ai’s own, recorded by this check 18 November at 23:06 UTC. Nothing here is a sample: name your own address and Xovris runs it for you.
Each technical word this page uses, said simply.