🤖 Overview

iCab is a legacy web browser and offline archiving tool developed by Alexander Clauss, first released in 1999 for classic Mac OS and later ported to macOS. Its primary purpose is to provide an alternative browsing experience with advanced download management and a built-in “Web Archiving” engine that can recursively crawl entire websites for offline storage. While iCab is used by human operators for personal browsing, its automated archiving feature functions as a legitimate, albeit aggressive, web crawler when invoked to capture site content. The software is maintained at icab.de and is not associated with any commercial search engine or AI training pipeline.

🌐 Technical Behavior

When operating in archiving mode, iCab issues sequential GET requests following the site’s internal link structure, typically starting from a user-specified URL and respecting relative and absolute hyperlinks. The crawl depth and maximum number of pages are configurable by the user, with defaults often set to unlimited depth, making it potentially aggressive on large sites. iCab uses standard HTTP/1.1 and HTTPS, and its request frequency is determined by the operator’s settings – typically one request per second or faster unless throttled manually. IP ranges correspond to the client machine’s public IP, as iCab runs on the user’s local device; there are no fixed cloud IP ranges. The tool supports cookies, JavaScript rendering (via WebKit), and can download embedded resources such as CSS, images, and scripts to preserve page fidelity.

📋 robots.txt Compliance

According to the official iCab documentation (icab.de) and community discussions, the archiving feature honors robots.txt directives by default, pausing when a Crawl-Delay directive is encountered and skipping pages marked Disallow. However, users can disable robots.txt compliance in the preferences, meaning the agent’s behavior is ultimately operator‑controlled. This dual-mode compliance makes iCab less predictable than dedicated bots with fixed policies.

🔍 Detection Indicators

The standard User‑Agent string for iCab is Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) iCab/5.1 (version varies). Archiving requests often appear with a Referer header matching the parent page and may include an Accept header of text/html,application/xhtml+xml. Behavioral fingerprints include high burst rates (if the user sets no delay), lack of a persistent user‑agent rotation, and simultaneous downloads of page resources (up to 4 concurrent connections per host, per the default configuration).

📊 Data Usage

Data collected by iCab is stored locally on the operator’s machine as a static archive (HTML, images, and supporting files) for offline browsing, research, or personal reference. No data is transmitted to any central server or used for AI training, search indexing, or analytics. The tool is purely a client‑side utility for content preservation, with no cloud component or data sharing.

⚙️ Rate Limiting Policy

iCab’s archiving mode should be rate‑limited because, without user‑imposed throttling, it can overwhelm small or medium‑sized websites by flooding requests. A threshold‑based block (e.g., 20 requests in 10 seconds from the same IP) is prudent to protect server resources while still allowing legitimate human browsing via the same browser.

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