🤖 Overview

EnaBot is the official web crawler operated by Ena Search (enase.org), a privacy-focused search engine launched in 2021. Its primary purpose is to discover and index publicly accessible web pages to power Ena’s search results, which emphasize user privacy and avoid personalized tracking. According to Ena’s official documentation (enase.org/crawler), the bot is designed to be transparent and respectful of website owners’ wishes.

🌐 Technical Behavior

EnaBot performs both incremental and full crawls, typically sending requests at a rate of 1–2 requests per second per IP, as stated in its Crawl-Delay directives. It uses HTTP/1.1 and HTTP/2 protocols, with a preference for IPv6 when available. IP ranges are drawn from Ena’s cloud infrastructure, which includes addresses announced via ASN 215338 (Ena Search Ltd). The crawler follows sitemaps and respects If-Modified-Since headers to reduce load. It also supports the Accept-Encoding: gzip header to minimise bandwidth consumption. EnaBot’s crawling queue is prioritised by page freshness and inbound link popularity, similar to other modern search engine bots.

📋 robots.txt Compliance

EnaBot fully honours the Robots Exclusion Standard, including Disallow directives, Crawl-Delay, and Allow overrides. Ena’s GitHub repository (github.com/enasearch/crawler-policies) confirms that the bot reads robots.txt at least once per domain per crawl session. In controlled tests, websites that set a Crawl-Delay: 5 saw EnaBot wait exactly five seconds between requests, demonstrating strict compliance.

🔍 Detection Indicators

The primary User-Agent string is EnaBot/1.0 (compatible; Ena Search; +https://enase.org/bot). Some instances also include a version suffix like EnaBot/2.0. The bot typically sets the From header to [email protected] and identifies itself via reverse DNS lookups with .crawl.enase.org PTR records. Behavioral fingerprints include a consistent request interval and the absence of JavaScript execution.

📊 Data Usage

Collected data is used exclusively for building and maintaining Ena’s search index. Ena explicitly states that it does not use crawled content for AI training or large language model development, as per its privacy policy (enase.org/privacy). The index is updated weekly, and page snippets are stored temporarily for search result displays. No user-level analytics are derived from crawled pages.

⚙️ Rate Limiting Policy

Although EnaBot is legitimate and rate-limited by design, aggressive crawling patterns from many simultaneous instances can still overwhelm smaller servers. Administrators should apply threshold-based rate limiting (e.g., 5 requests per second per IP) to protect backend resources while allowing the bot’s intended crawl speed. Ena provides a rate-limit profile at enase.org/crawler#limits to help server operators configure appropriate rules.

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