Feature

DNS & network

Below the website there is a domain, and a domain can be moved out from under you without a single byte of the site changing.

What it does

zutpralik records what your DNS resolves to and tells you when it changes. An A record that suddenly points elsewhere, nameservers that are not the ones you set, an MX record quietly rewritten — these are the fingerprints of a hijacked domain, and they are usually noticed far too late.

The same check doubles as an early-warning system for ordinary mistakes: a migration where one record was missed, a TTL change nobody announced, a staging value pushed to production.

Underneath the DNS layer, TCP-port and ICMP checks confirm that the host itself is reachable, which is what separates “the web server has crashed” from “the whole machine is gone”.

  • A / AAAA / MX / NS change detection
  • Alerts on nameserver drift — the classic hijack signal
  • TCP-port reachability for any port you depend on
  • ICMP ping checks for the host behind the site
  • SMTP checks for the mail server that carries your client’s business

FAQ

About dns & network

Why does a changed NS record matter so much?

Whoever controls the nameservers controls where the domain points, including mail. A nameserver change you did not make is one of the strongest signals that a registrar account has been compromised.

Will DNS propagation set off false alarms?

The check compares against the last recorded answer, so an intentional migration registers once as a change rather than repeatedly. You confirm it and the new value becomes the baseline.

Can I monitor a port that is not a website?

Yes — TCP-port checks work against any port you nominate, which covers mail, databases and internal services exposed to the internet.