Most blacklist tools ask you for an IP address. That is the wrong unit for a website owner: you know
your domain, your hosting provider owns the IP, and the IP can change under you without anyone telling
you. HostTracker monitors the domain. On every run it resolves the name first and then
tests the addresses that are actually behind it right now, so a move to a new server or a new mail
provider is picked up automatically instead of leaving you watching an address you no longer use.
Which addresses get tested is a per-monitor setting. The default checks the first A record - the
machine that serves your website. The second mode checks every A record, which is what you want
when the domain is spread across several front ends. The third follows the mail path: it looks up your
MX hosts and checks the addresses behind them, because those are the addresses a receiving mail server
inspects when it decides whether to accept your message. If email deliverability is the reason you are
reading this page, that is the mode to pick.
One distinction worth being precise about, because plenty of pages are vague on it. There are two
different families of list. IP-based lists (the DNSBLs - Spamhaus, SpamCop, Barracuda,
SORBS and dozens more) list the address that sent the mail, and those are what HostTracker's blacklist
monitoring queries. Domain-reputation lists (DBL, SURBL, URIBL) list the domain name
itself as it appears inside a message body, which is a separate mechanism with separate operators;
HostTracker does not query those zones. What "domain blacklist monitoring" means here is therefore
precise: you give us a domain, we keep the addresses behind it out of trouble.
The immediate cost of a listing is mail. Messages from a listed address are rejected outright or
quietly filed as spam, and because nothing bounces back to you in the second case, the first symptom is
usually silence - invoices that were never read, password resets that never arrived. Reputation damage
of the other kind, the red browser warning that costs you visitors and search traffic, comes from a
different check: malware and phishing monitoring against Google's
Web Risk database, which most accounts run alongside this one.