DNSToolboxBot
If you found this User-Agent in your logs or your firewall, this page explains what it is, why it visited, how to recognise it, and how to allow it or stop it.
What it is
DNSToolboxBot is the monitoring and scanning agent of DNS Toolbox. It never crawls the web looking for sites. It visits a site only because a DNS Toolbox user asked us to check that site — usually its owner or the people who look after it.
What it does
- Uptime checks. One
GETorHEADof a single URL every few minutes, reading at most 256 KB — or a TCP connect to the one port the user entered, sending nothing, or two ICMP echo requests (ping) — from one of our monitoring locations (Frankfurt, New York or Singapore — the addresses below). This is the traffic you will see most. - Scans. When a user runs a scan, or a rescan they scheduled: a handful of requests, once — the homepage over HTTPS and HTTP, with and without
www;robots.txtand at most three sitemap addresses (those it lists, or/sitemap.xml,/sitemap_index.xmland/wp-sitemap.xml); the TLS certificate, read with one ordinary handshake; and, only when the domain publishes an MTA-STS record, its policy file athttps://mta-sts.<domain>/.well-known/mta-sts.txt. DNS, registration (RDAP and WHOIS) and blocklist lookups are made elsewhere and never touch your server. - WordPress exposure checks. Part of a scan, and only when the homepage is a WordPress site: one
GETeach of/readme.html,/wp-json/wp/v2/users,/?author=1(its redirect is not followed),/xmlrpc.phpand/wp-content/uploads/, and of five files that are sometimes left behind by mistake —wp-config.php.bak,wp-config.php~,.wp-config.php.swp,wp-content/debug.logand.git/config. Each response is cut off early (at 96 KB at most, and at 4 KB for those five files) and read only to tell the real thing from an error page. Nothing is posted, no login is tried, and a file's contents are never stored or shown: the report says only that it can be downloaded, so its owner can remove it. - WordPress health and management. Only for a site its administrator connected to DNS Toolbox, in one of two ways. With an application password they created for us, we send only
GETrequests to the REST API. With the DNS Toolbox Connector plugin they installed and paired with a one-time code, every request is signed, dated and usable once, and the site's owner can — from their DNS Toolbox account — update plugins, themes and WordPress (with a snapshot and automatic rollback), take and restore backups, and manage plugins, themes and users. Deactivating the plugin ends that access at once. These requests come from one of our monitoring locations, like uptime checks. - Site audit crawler. When a user asks for one: a bounded number of pages at a polite rate. It honours
robots.txtrules forUser-agent: DNSToolboxBot. It crawls from one of our monitoring locations (the addresses below), one request at a time with a pause between them, and stops by itself if your firewall starts refusing it.
What it never does
No vulnerability exploitation or attack payloads, no password guessing or login attempts, no fuzzing and no guessing of paths beyond the fixed list above, no port scanning, and no attempt to get past a firewall, CAPTCHA or bot challenge — a challenge or a refusal is reported to our user as blocked, with the addresses on this page to allow. We follow redirects only within HTTP and HTTPS, never send credentials anywhere except to a site whose administrator connected it, and back off automatically when a site answers 403 or 429 — repeated checks against a firewall that is rejecting us help nobody.
Visits made on our behalf by others
- Outage confirmation. When none of our locations can reach a site, we may ask Globalping, a public measurement network, to request the same address once, to tell a site that is down from one that only blocks us. That request comes from Globalping's probes, not from the addresses below.
- Performance checks are run by Google PageSpeed Insights, so those visits come from Google (a User-Agent containing
Chrome-Lighthouse), not from us.
How to recognise it
- User-Agent
DNSToolboxBot/1.0 (+https://dnstoolbox.app/bot)- Addresses
-
IP address Role 185.73.9.5Monitoring 185.111.111.162Monitoring 79.127.219.200Monitoring 169.150.207.218Monitoring Machine-readable list: https://dnstoolbox.app/bot/ips.txt (one address per line). We add addresses here before they start checking anything. Any of them may be the one that visits: checks run from the monitoring location nearest the site, and when a site refuses one of these addresses the check is made from another of them instead — never from an address that is not listed here — so allow the whole list rather than a single address.
Allow by IP address, not by User-Agent. Anyone can send any User-Agent string. Only the addresses above are ours.
How to allow it
If DNS Toolbox tells you a site is blocked — or you connected a site and it cannot be reached — your firewall is rejecting the addresses above. Allowing them is a one-line change in most tools:
- Cloudflare. Security → WAF → Tools → IP Access Rules: add each address with the action Allow. If you use a managed challenge on the whole site, add a custom rule that skips challenges for these addresses.
- cPanel with CSF / ConfigServer. As root:
csf -a 185.73.9.5 DNSToolboxBot, or add the address under Quick Allow in the ConfigServer WHM plugin. - Imunify360. Firewall → White List → add the address. Also add it to the Proactive Defense ignore list if you use it.
- Wordfence. Firewall → All Firewall Options → Allowlisted IP addresses that bypass all rules.
- Sucuri firewall. Firewall → Access Control → Allow IP addresses.
- Plain Apache / LiteSpeed. In
.htaccess, before any deny rules:<RequireAny> Require ip 185.73.9.5 Require ip 185.111.111.162 Require ip 79.127.219.200 Require ip 169.150.207.218 </RequireAny>
How to stop it
- The site audit crawler obeys
robots.txt:User-agent: DNSToolboxBot Disallow: /
- Scans, uptime checks and WordPress health exist because a DNS Toolbox user asked for them for your site. Blocking our addresses stops them immediately; we will notice and stop retrying at the normal rate. If you would rather we removed the checks, write to us at info@dnstoolbox.app with the hostname and we will take care of it.