🤖 Overview

Antro Net is a web crawler operated by Antro.net, a Russian-language search engine launched in 2019 that indexes web content primarily from Russia and Eastern Europe for general search results. According to the official Antro.net documentation, the crawler’s purpose is to build a comprehensive searchable index of publicly available web pages for users accessing the Antro search service.

🌐 Technical Behavior

The Antro Net crawler uses a proprietary HTTP-based crawling algorithm with a configurable request rate typically set to one request every 2–5 seconds per host to avoid server overload. Its IP ranges are allocated from Russian RIPE blocks (e.g., 95.213.0.0/16 and 185.158.0.0/18) and are published in the Antro Net crawler IP list available at https://www.antro.net/crawler-ips. The crawler supports both HTTP/1.1 and HTTP/2 protocols, and sends a custom User-Agent string without the “Mozilla” prefix, making it identifiable in server logs.

📋 robots.txt Compliance

Antro Net explicitly honors Disallow directives in robots.txt as stated in its crawler policy. Official documentation confirms that it checks robots.txt before each crawl session and will not access disallowed paths; violations are reported to the bot operators.

🔍 Detection Indicators

The primary User-Agent string is “Antro/1.0” (full: “Antro/1.0 (https://www.antro.net/bot)”) along with variations like “AntroNet” or “Antro-Bot”. No X-Robots-Tag header is sent, but the crawler includes a From header with the bot email [email protected]. Behavioral fingerprints include sequential GET requests without cookies or session headers.

📊 Data Usage

Collected data is used exclusively for indexing in the Antro.net search engine to provide Russian-language search results. Antro.net states that content is not used for AI training, advertising profiling, or third-party redistribution — only for search query matching and snippet generation.

⚙️ Rate Limiting Policy

Although legitimate, Antro Net’s aggressive default crawl speed can overwhelm small sites; therefore, rate limiting is justified to maintain server stability. A threshold of 10 requests per minute per IP is recommended for blocking only when automated abuse misconfiguration is suspected.

ⓘ 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.