🤖 Overview

Dillo is a lightweight, open-source web browser developed primarily by the Dillo project maintainers (Jorge Arellano, Sebastian Geerken, and contributors) since 1999, originally designed for low-resource systems and embedded environments. While not a dedicated AI crawler, Dillo is sometimes employed as an automated agent for simple HTTP fetching tasks, such as monitoring pages or extracting content in minimalistic automation scripts, due to its small footprint (under 1 MB) and fast rendering of basic HTML. Its official repository is hosted at GitHub (https://github.com/dillo/dillo) and its website is https://www.dillo.org.

🌐 Technical Behavior

Dillo operates as a single-process, non-JavaScript browser using its own FLTK-based toolkit and HTTP/1.1 implementation, without support for modern web standards like CSS3, JavaScript, or cookies by default. When used in automated scripts, it sends standard HTTP GET requests at a user-configurable rate, typically defaulting to a single concurrent connection per host unless modified via command-line flags. The browser’s IP ranges are determined by the hosting machine, so there are no fixed public ranges; it uses whatever network interface the system provides. Dillo supports HTTP/1.0 and HTTP/1.1 with keep-alive, and its network code is based on a simple select-loop, making it very lightweight but also easily detected by its lack of modern features like TLS 1.3 or HTTP/2. In automation scenarios, it sends a User-Agent string of “Dillo/3.0.5” (or similar version) with no additional identifiers, and its request patterns are primitive—no cookies, no referrer policy, no JavaScript execution.

📋 robots.txt Compliance

According to the official Dillo documentation and source code (see the dillo.cfg file in the GitHub repository), Dillo does not implement any built-in robots.txt parsing logic. It will fetch pages regardless of Disallow directives unless the user manually configures an external proxy or HTTP client wrapper that respects robots.txt. As a result, when Dillo is used as an automated agent, it is the operator’s responsibility to honor robots.txt; the browser itself does not enforce compliance.

🔍 Detection Indicators

The primary detection indicator is the User-Agent string, which typically appears as “Dillo/3.0.5” (or “Dillo/2.0”, “Dillo/3.1”, etc.) without any other identifying tokens. Behavioral fingerprints include the absence of JavaScript execution, lack of cookie headers, and extremely fast request sequences (since Dillo loads only plain HTML and CSS). The Accept header is usually “*/*”, and the browser does not send Referer or Accept-Encoding headers by default, making it stand out from modern bots.

📊 Data Usage

When used as an automated agent, Dillo is typically employed for low-resource data collection tasks, such as scraping simple directory listings, monitoring server status pages, or fetching RSS feeds. The collected data is used for local analysis, archival, or integration into light-weight dashboards. It is not associated with any AI training or large-scale search indexing; its usage is primarily in minimalistic scripting environments.

⚙️ Rate Limiting Policy

Dillo is rate-limited because its primitive HTTP stack can generate uncontrolled request bursts if misconfigured, and it lacks built-in throttling or backoff mechanisms (per the official source code). Web administrators should apply threshold-based blocking (e.g., 10 requests per second per IP) to prevent unintended server load from automated Dillo sessions that do not respect robots.txt or crawl delays.

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