🤖 Overview

internetVista monitor is a legitimate web crawler operated by internetVista SAS, a French website monitoring company founded in 2002 and later acquired by Uptrends in 2020. Its primary purpose is to continuously verify website availability, response times, and content integrity from multiple global vantage points, feeding performance data into the internetVista SaaS platform for alerting and reporting. According to the official internetVista support documentation, the bot performs periodic HTTP requests to simulate real user visits and detect downtime or degradation.

🌐 Technical Behavior

The crawler sends requests at configurable intervals, typically ranging from 1 minute to 60 minutes per monitored URL, depending on the customer subscription. It uses both IPv4 and IPv6 addresses drawn from a published list of monitoring nodes located across Europe, North America, and Asia (over 15 locations as of 2025). The bot fully supports HTTP/1.1 and HTTP/2, follows redirects, and can handle JavaScript-rendered content when enabled. It respects standard HTTP methods (GET, HEAD, OPTIONS) and typically sends a single connection per check without concurrent requests to avoid overloading servers. Official IP ranges are documented at https://www.internetvista.com/en/faq/monitoring-ip-addresses/.

📋 robots.txt Compliance

internetVista monitor is documented to respect robots.txt directives. The official internetVista FAQ states that the bot reads the robots.txt file before crawling and will honor Disallow rules. However, note that the bot is primarily checking page availability, not indexing content, so some webmasters may choose to allow limited access while disallowing deep paths. The company urges customers to add the User-Agent line User-agent: InternetVista monitor to control access, but by default it will obey standard instructions.

🔍 Detection Indicators

The primary User-Agent string is "InternetVista monitor/1.0" (or variants like "InternetVista Monitor"). Additional behavioural fingerprints include a sequential IP pattern from the published monitoring node ranges, a low request rate (single burst followed by a long idle period), and a missing Referer header. The bot may also include a X-InternetVista-ID header in some cases, though not widely documented. Server logs can identify it by the combination of User-Agent and the exact timing intervals set in the monitoring plan.

📊 Data Usage

Collected data is used exclusively for website monitoring and performance analytics. internetVista records response status codes, response times (including DNS lookup, TCP connection, SSL handshake, and page load), and checks for specific keywords or content changes. This data is aggregated into uptime reports, SLA compliance dashboards, and real-time alerts sent via email, SMS, or webhooks. No data is used for AI training, search indexing, or any secondary commercial purpose—the service is purely for operational monitoring.

⚙️ Rate Limiting Policy

Rate limiting for internetVista monitor is justified because its monitoring frequency can generate repeated requests at short intervals (e.g., every 60 seconds) that may be mistaken for aggressive crawling. Blocking the bot entirely is discouraged as it would prevent legitimate uptime monitoring; instead, webmasters are advised to implement threshold-based rate limiting on a per-IP basis (e.g., 60 requests per hour from a single monitoring node) to protect against misconfigured high-frequency checks while allowing essential health probes.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.