How it works
Every 2 hours, we look up your DNS records and compare them with the previous run:
A,AAAAandCNAMEfor your host: where the site is served from;NS,MX,TXTandCAAfor your domain: who answers for the domain, where email goes, and verification and security records.
The first run records a baseline. After that, every change is reported with its before and after values. Unexpected changes can mean a hijacked domain, a DNS provider mistake or a migration that went wrong, and they often explain why your site or email suddenly stopped working.
Statuses
| Status | Meaning |
|---|---|
| OK | No records changed since the previous run. |
| Warning | Records changed (the report lists them), or a lookup failed. |
By default you are notified of warnings and failures.
What to do
- You made the change: nothing to do. The next run uses the new records as the baseline.
- You did not: compare the new values with what you expect. Check your DNS provider's audit log and your registrar account for unauthorised access.
- Load-balanced sites: some load balancers rotate their IP addresses, which shows up as frequent
Arecord changes. If that is noisy, lower this check's notification level.