What InternetMeasurementBot does
InternetMeasurementBot is run by driftnet.io to discover and measure services that network owners and operators have publicly exposed, giving administrators an external view of their infrastructure. The operator states that its traffic is not an attack and will never attempt to log in to your systems. It performs no site crawling, and authentic traffic comes only from the operator's published IP ranges. The domain's SPF, DKIM, and DMARC records mark internet-measurement.com as unable to send email.
How to control InternetMeasurementBot
Target InternetMeasurementBot in your robots.txt with the InternetMeasurement token. Rules apply per bot, so you can allow this one while blocking others, or the reverse.
Allow InternetMeasurementBot
User-agent: InternetMeasurement
Allow: /Block InternetMeasurementBot
User-agent: InternetMeasurement
Disallow: /Driftnet publishes the IPv4 and IPv6 ranges its scanner uses (for example 87.236.176.0/24 and 185.247.137.0/24) and states that authentic traffic comes only from those ranges.
How to identify InternetMeasurementBot
Temso identifies InternetMeasurementBottraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
InternetMeasurementInternetMeasurementBot FAQ
What is InternetMeasurementBot?
InternetMeasurementBot is a scanner operated by driftnet.io that discovers and measures publicly exposed services to give network owners an external view of their infrastructure. Its operator states the traffic is not an attack and never attempts to log in to systems.
How do I block InternetMeasurementBot?
You can add a robots.txt group with 'User-agent: InternetMeasurement' and 'Disallow: /', but the operator states it does not perform any form of site crawling. The documented ways to stop the traffic are blocking its published IP ranges or contacting the operator with your IP ranges and domain names to request an opt-out.
About Operational Bots
Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.
Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.
