How it works

Why NSvera isn't cached, in plain English.

The problem with other checkers

When you look up a domain, you normally ask a "resolver" (your internet provider, Google, Cloudflare). Resolvers remember answers for a while so they are fast. The catch: after you change a record, they can keep handing out the old one until their copy expires. That can be minutes or a day.

What NSvera does instead

1. Asks all 13 root servers who runs your domain ending (for example .au), and checks they agree.
2. Asks every server of your registry which nameservers your domain uses, and checks they agree.
3. Asks each of your nameservers directly for your records: website, email, security and more.
4. Compares every answer. If one nameserver is behind or different, we highlight it.

Every question is sent with "recursion" turned off, which means "answer only from what you hold yourself". We only trust answers marked authoritative. Nothing is stored between checks, so refreshing the page runs the whole thing again, live.

What the results mean

Pass: all good. Warning: works, but could cause problems. Fail: something is broken and should be fixed. Info: for your information only. Every warning and fail tells you what it means and how to fix it.

For developers

The same data is available as JSON: https://nsvera.com/api/check?d=example.com.au