Monitoring 47

SmartBear Software · Monitoring

SmartBear's AlertSite runs customer-configured availability and transaction monitors against the sites and APIs their owners point it at, from a published set of monitoring locations. SmartBear tells site owners to filter the traffic by looking for "AlertSite" in the user agent string or by the monitoring location addresses. Some mobile-network locations use dynamic carrier addresses that are not in the published list.

Awario · Monitoring

Awario's social-listening and media-monitoring crawlers, which fetch web pages and RSS feeds to find mentions of the brands and keywords its customers track. Awario states the bots respect robots.txt and honour Crawl-delay, and explicitly asks site owners not to identify them by IP because it uses no consecutive IP blocks.

Microsoft · Monitoring

Synthetic availability-test agents from Microsoft Azure Application Insights that send recurring HTTP requests to user-configured URLs to monitor uptime and responsiveness from multiple Azure regions.

Better Stack · Monitoring

Better Stack's uptime-monitoring probes, which request customer URLs on a schedule from a published, frequently-changing list of monitoring IPs.

BrandVerity · Monitoring

BrandVerity is a brand-protection service that crawls websites and paid search landing pages to detect trademark and affiliate-compliance violations on behalf of its clients.

Brandwatch · Monitoring

magpie-crawler is Brandwatch's web crawler. It downloads publicly available blog, forum, news, and social-media pages to be indexed and analysed by Brandwatch's social-listening platform. It respects robots.txt.

Checkly · Monitoring

Synthetic-monitoring service that runs API and browser checks against customer endpoints from a published, fixed set of static outbound IPs.

Cloudflare · Monitoring

Cloudflare's support-diagnostics fetcher. Cloudflare documents that requests with this user agent are triggered when Cloudflare Support Engineers perform error checks, and by the continuous monitoring that raises alerts in the Cloudflare dashboard.

Cloudflare · Monitoring

Cloudflare's Health Checks probes, which monitor customer origin servers from Cloudflare data centers in regions the customer selects. Cloudflare documents a fixed User-Agent format embedding the first 16 characters of the health check ID, and recommends matching on it; its health-checks docs do not tie probe traffic to the published Cloudflare IP lists, so no CIDR recipe is attached.

Cloudflare · Monitoring

Cloudflare's prefetch bot, an Enterprise speed-optimization feature that pre-populates the CDN cache with content a visitor is likely to request next, using a site-owner-supplied manifest of URLs. Requests carry the CloudFlare-Prefetch user-agent.

Cloudflare · Monitoring

Cloudflare's Load Balancing monitor, which sends health-check requests to customer origin pools at regular intervals to evaluate endpoint health. It embeds the load-balancer pool id in a fixed User-Agent.

Cookiebot (Usercentrics) · Monitoring

Cookiebot's cookie-consent compliance scanner. It crawls the domains its customers have registered, on a roughly monthly schedule, to detect the cookies and tracking technologies in use and generate a cookie declaration. Cookiebot documents that scans run only from a fixed pool of addresses.

CookieHub · Monitoring

CookieHub's cookie-consent compliance scanner. It crawls customer domains on a roughly monthly schedule to detect cookies and tracking technologies in use and generate a compliance report.

Datadog · Monitoring

Datadog Synthetic Monitoring probes that run customer-configured API and browser tests against endpoints. API tests send a "Datadog/Synthetics" User-Agent; browser tests append "DatadogSynthetics" to a browser UA. Datadog publishes probe IP ranges as a machine-readable feed at ip-ranges.datadoghq.com/synthetics.json.

DLC Websites · Monitoring

Dead Link Checker is a hosted service that crawls a submitted website to find broken links and report them, with paid tiers that run automated periodic scans and email the results.

DubBot · Monitoring

The crawler behind DubBot's web-governance platform. It inventories a customer's own website by following every link from a supplied URL and checks the pages for accessibility, broken links, spelling and content-policy problems. DubBot runs it from AWS on static IP addresses that the operator publishes for allowlisting.

Dynatrace · Monitoring

Dynatrace's synthetic monitoring runs browser and HTTP checks against sites its customers configure. Dynatrace always appends a RuxitSynthetic token to the user agent — even when the customer sets a custom one — so that synthetic traffic can be identified in server logs. Checks are user-configured, not crawling, so robots.txt is not part of the documented behaviour.

Fed Reporter Inc. · Monitoring

Scheduled data-retrieval bot that pulls publicly available banking-institution records from the FFIEC National Information Center for Fed Reporter's internal research dashboards. Its documentation states it targets only public data, uses no CAPTCHA bypass, and runs a separate testing agent off-peak.

GreenWave Online Inc. · Monitoring

The website-monitoring robot of the FreeWebMonitoring service. It only checks URLs that registered members have submitted, and the operator documents that all checks originate from a single server address. GreenWave Online also warns that an older 0.1 agent name is forged by an unrelated scanner.

Freshworks · Monitoring

Freshworks' free uptime-monitoring service, which checks customer sites from a small, fixed set of documented monitoring-location IPs rather than a live feed.

Ghost Inspector · Monitoring

Ghost Inspector runs customer-authored browser tests against the sites their owners point it at, from a fixed pool of cloud test runners in 18 regions. Its runners append the literal string "Ghost Inspector" to the browser user agent they run, and the operator publishes the full list of test-runner addresses so site owners can filter the traffic out of their analytics.

Gnowit · Monitoring

Gnowit is an Ottawa-based media and government monitoring company whose crawler continuously fetches news, government, and other public web sources to power real-time monitoring, summarization, and analytics for its clients.

Grafana Labs · Monitoring

Grafana Cloud Synthetic Monitoring public probes, which run customer-configured checks (HTTP, browser, and protocol) from Grafana-run locations. HTTP checks send a documented synthetic-monitoring-agent User-Agent by default (customers can override it). Grafana publishes probe source IPs as a machine-readable feed at allowlists.grafana.com/synthetics.

HetrixTools · Monitoring

Uptime and blacklist monitoring service that probes customer sites from a published list of monitoring-node IPs.

Hydrozen · Monitoring

Hydrozen.io is an uptime and website monitoring service; its checker fetches monitored endpoints from a documented, published set of IP addresses.

Hypefactors · Monitoring

Buck is Hypefactors' media-monitoring crawler. It discovers and indexes web pages by following links, gathering publicly available content for the company's media-monitoring platform. It identifies itself and respects robots.txt.

Automattic · Monitoring

Jetpack's site uptime monitor, operated by Automattic for WordPress sites that enable Jetpack Monitor. It sends an HTTP HEAD request to the site's homepage every five minutes; if that check fails, three further servers in other locations re-check before the site is reported down.

MediaMonitoringBot · Monitoring

Crawler behind MediaMonitoringBot, a Ukrainian media-monitoring service that indexes news and media publisher pages and delivers mention alerts to PR and communications subscribers. The operator documents that it strictly respects robots.txt allow and disallow rules, publishes its main crawler addresses, and documents a reverse-DNS suffix for verification.

Determ · Monitoring

Mediatoolkitbot is the web crawler operated by Determ (formerly Mediatoolkit), a media monitoring platform. It fetches publicly available web content to match brand mentions and topics that Determ's customers track.

Neticle Technologies · Monitoring

Neticle's in-house crawler for its social and online media-monitoring service. It continuously fetches newly published web content so Neticle can score sentiment around the keywords, brands and products its customers track.

New Relic · Monitoring

New Relic's synthetic-monitoring minions, which probe customer-configured URLs from public minion IPs. New Relic documents an X-Abuse-Info request header identifying the monitor and account; logs also record a NewRelicbot User-Agent. New Relic states the published ranges "are reserved for use by New Relic and cannot be used by anyone else". The published IP list is a JSON object keyed by location, which this directory's feed formats cannot consume, so the ranges are recorded statically instead.

ObservePoint · Monitoring

ObservePoint's web-governance platform runs customer-configured audits and user journeys against their own sites to validate analytics and marketing tags. Requests come from a published set of static addresses that the operator states are used by ObservePoint alone, and most of its browser-based user agents carry the literal name "ObservePoint".

SolarWinds · Monitoring

Uptime and page-speed monitoring service that probes customer sites from a published list of probe-server IPs. Owned by SolarWinds.

Amazon Web Services · Monitoring

Amazon Route 53 health checkers, which probe customer-configured endpoints from AWS data centers worldwide to drive DNS failover. AWS publishes the checker source ranges only inside the general ip-ranges.amazonaws.com feed, tagged with the ROUTE53_HEALTHCHECKS service, which this directory's feed formats cannot filter on, so the ranges are recorded here as a snapshot instead. AWS documents that it rarely changes them.

Scrunch AI · Monitoring

Fetcher for Scrunch AI's brand-visibility product. Scrunch documents that it accesses customer websites to diagnose issues with their content and configuration, and that it does not proactively crawl or spider the general internet — requests are made only in response to customer configuration.

SentiOne · Monitoring

SentiOne's social-listening crawler. It indexes user-generated content for the SentiOne Listen platform, which its operator says analyses over 300,000 domains daily. Robots.txt rules written for "sentibot" are honoured, and Yandex-style reverse-DNS plus a published IP list allow verification.

Sentry · Monitoring

Sentry's uptime monitoring bot, which probes customer-configured URLs on a schedule from Sentry's uptime-check infrastructure and raises alerts on failures. Sentry documents a fixed User-Agent and publishes the current uptime-check IP addresses at a machine-readable endpoint.

Zoho · Monitoring

Zoho's infrastructure and website monitoring service, which probes customer sites from 130+ global monitoring locations published as a machine-readable IP list.

Spectate · Monitoring

Spectate's uptime and performance monitoring agent. It requests the URLs a Spectate customer has added to their monitors, from fixed probe locations, to check that the target is reachable. Spectate publishes the addresses those probes request from as a plain-text list grouped by location.

StatusCake · Monitoring

Uptime and page-speed testing service that requests customer URLs from a global network of test-location servers, published as a machine-readable IP list.

Testomato · Monitoring

Testomato's website-monitoring agent. It downloads pages and resources and submits web forms for the checks its customers configure (uptime, error, SSL, response-time, meta-tag and JSON-LD monitoring), on a schedule the customer sets. Testomato publishes a plain-text list of the addresses its monitoring nodes request from.

Trendiction · Monitoring

Trendiction operates a crawler that fetches public news sites, message boards, and blogs to build a search index and feed media-monitoring and market-research analytics for its clients.

updown.io · Monitoring

Website uptime-monitoring service that checks customer sites from a published JSON array of node IPs. Documents "updown.io" as the common substring of its requests rather than one fixed User-Agent.

Uptime.com · Monitoring

Uptime.com's synthetic-monitoring probes. They request the URLs its customers configure as checks, from probe servers in many locations, including headless-browser transaction checks that execute JavaScript. Uptime.com publishes its probe IP list only inside the authenticated dashboard, so the user agent is the public identifier.

UptimeRobot · Monitoring

Uptime monitoring service that probes customer sites on a schedule from a published list of monitoring IPs.

WEBSPARK (W.A.R.D.) · Monitoring

The monitoring agent behind W.A.R.D. It requests URLs that users have added to their monitoring list and records the HTTP status code so the user can be notified of downtime, at an average frequency of ten minutes or more per URL. The operator documents that its addresses reverse-resolve under the robot.ward.host suffix.

WatchFor · Monitoring

WatchFor's monitoring probe, which checks that websites, APIs, servers and certificates its customers have configured are healthy, from fixed locations worldwide. It performs only the specific check each monitor defines and does not crawl sites, follow links or harvest content. WatchFor publishes a machine-readable address list and forward-confirmed reverse DNS under probe.watchfor.io so site owners can tell a genuine probe from a spoofed user agent.