WebCheck DNS checks resolve the target hostname and record normalized A, AAAA, CNAME, MX and NS records. The first successful result establishes a reference; a later record change is reported for review.
Records WebCheck records
The DNS inspector normalizes and sorts supported records before calculating a record hash. This helps avoid reporting a change just because records were returned in a different order. TTL values are not included in the DNS evidence.
First run and later runs
The first successful DNS result establishes the reference. A later difference is recorded as a DNS-records-changed failure. Review the records in the run evidence and compare them with the DNS provider's current configuration and change history.
WebCheck does not currently offer a dashboard control to accept a new DNS baseline. If a planned DNS migration causes a reported change, keep the related change record and check results together while you investigate.
What to do after a change
Check the DNS provider change history and recent hosting or CDN work. Compare the records WebCheck reported with the provider's current configuration and allow for resolver caching when interpreting a recent change.
Important limitation
One monitoring environment cannot represent every resolver everywhere. DNS propagation and caching can make results differ temporarily from a lookup on your own computer. WebCheck's DNS check also does not replace a full DNS security or email-configuration audit.