For your hosting provider
If TLDTrack reports your site as down when it is not, your host or security software is likely blocking us. Allowlist the IPs below so our checks get through.
01 · Allowlist
Required for monitoring
18.168.0.190Recommended
35.178.155.62The US East and Singapore uptime confirmations, visual captures and journey tests run from AWS addresses that change between runs, so there is no fixed IP to allowlist for those.
02 · How-tos
WHM (GUI):
CLI (SSH as root):
imunify360-agent ip-list local add --ip 18.168.0.190 --comment "TLDTrack uptime"
imunify360-agent ip-list local add --ip 35.178.155.62 --comment "TLDTrack dashboard"WHM (GUI):
CLI (SSH as root):
csf -a 18.168.0.190 "TLDTrack uptime"
csf -a 35.178.155.62 "TLDTrack dashboard"
csf -r/usr/local/lsws/conf/httpd_config.conf, find the accessControl block, and add:
allow 18.168.0.190, 35.178.155.62
systemctl reload lsws(ip.src eq 18.168.0.190) or (ip.src eq 35.178.155.62)
# iptables (insert at top of INPUT chain)
iptables -I INPUT -s 18.168.0.190 -j ACCEPT
iptables -I INPUT -s 35.178.155.62 -j ACCEPT
# UFW (Ubuntu)
ufw allow from 18.168.0.190
ufw allow from 35.178.155.62
# firewalld (RHEL/Rocky/Alma)
for ip in 18.168.0.190 35.178.155.62; do
firewall-cmd --permanent --add-rich-rule="rule family=ipv4 source address=$ip accept"
done
firewall-cmd --reloadEdit /etc/fail2ban/jail.local and append to the [DEFAULT] section:
ignoreip = 127.0.0.1/8 ::1 18.168.0.190 35.178.155.62
Then systemctl restart fail2ban
curl -s -o /dev/null -w "%{http_code}" -A "Mozilla/5.0 (compatible; TLDTrack-Uptime/2.0; +https://tldtrack.com/uptime)" https://your-domain/ - should print 200 or a 3xx redirect.Still seeing blocks after allowlisting? Get in touch and we'll help debug.
This cannot be undone.