Domain check

NS record monitoring

DoubleCheck compares the NS records of your domain with the name servers you expect, and alerts you when the delegation changes.

The problem

The NS records say which servers answer for your domain. They are set at your registrar, and changed when you move DNS to another provider.

A change at the registrar, by mistake or by someone else, moves your whole domain to other name servers. Websites and mail follow it.

Why it matters

Whoever controls the name servers controls everything in your domain. An unexpected name server is one of the first signs of a hijack.

After a migration the old name servers are often left in place. Records that disagree between old and new servers cause problems that come and go.

How to check it manually

Look up the NS records of a domain with dig or nslookup:

dig +short NS example.com
nslookup -type=NS example.com

How DoubleCheck checks it

DoubleCheck reads the NS records once a day and compares them with the name servers you entered. A missing one is an error, an extra one is a warning.

When you add the check through the wizard, the name servers that exist now are filled in for you. To see whether those name servers also answer and agree with each other, use the name server health check.

example.com 1 warning
Domain checks · 8 checks · once a day
SPF-all · 4 of 10 lookups
DKIM selector12048 bits
DMARCp=none · 1 report address
MX2 of 2 expected
NS2 of 2 expected
Name servers2 answer, same serial
Blacklistclean on 20 lists
Domain expiry287 days left
90 days agoOK Warning Not checked yettoday
Sample data. The domain checks of one domain, each with its last result and one square per day for the last 90 days. A new check starts grey.
Measures
A DNS NS lookup of your domain, compared with the name servers you expect.
Runs
Once a day. The interval is the same for every domain check: what it reads rarely changes.
Status
  • OK when the domain has NS records and every expected name server is present.
  • Warning when a name server appears that you did not expect, unless you accepted extra records.
  • Error when an expected name server is missing, or the domain has no NS record at all.
  • Unknown, and no alert, when DNS itself does not answer.
Options
  • Expected values: the name servers that must be there. Leave them empty to only check that the domain has NS records.
  • Records that are not expected: a warning by default. Choose "accept" to ignore them.
FAQ

Frequently asked questions

Can I enter more than one name server?

Yes, separate them with a comma. Every one must be present, and an extra one gives a warning.

Does this check whether the name servers work?

No, it only reads the delegation. Whether each name server answers is what the name server health check does.

Get started

Start monitoring with DoubleCheck

Start with €5 of free credit, no credit card required. Alerts by email, SMS, Slack, Microsoft Teams or Discord.

Start monitoring