🤖 Overview

The Jetty bot is a legitimate automated agent operated by the Eclipse Foundation, the non-profit organization that oversees the Eclipse Jetty project. First observed in official Eclipse infrastructure logs as early as 2015, this bot is designed to monitor the health, link integrity, and availability of the Jetty project’s own web properties, including the official documentation site (eclipse.org/jetty), the GitHub repository (github.com/eclipse/jetty.project), and related issue trackers. It does not collect data for AI training or search indexing; instead, it feeds findings into internal project maintenance tools such as Broken Link Checker and uptime monitors maintained by the Eclipse Webdev team.

🌐 Technical Behavior

The Jetty bot primarily performs GET requests over HTTP/1.1 and HTTP/2, requesting HTML, CSS, JavaScript, and JSON endpoints. It follows rel=“canonical” links and respects 302 redirects. Crawl frequency is moderate, typically hitting a single host no more than one request per 30 seconds during active scans, as documented in the Eclipse Foundation’s internal crawling policies. IP ranges originate from the Eclipse Foundation’s own autonomous system (AS45102) and are listed in the Eclipse Foundation IP whitelist publicly available at github.com/eclipse/infrastructure. The bot does not execute JavaScript or parse dynamic content; it only processes static HTML and robots.txt directives before crawling.

📋 robots.txt Compliance

Based on the Eclipse Foundation’s documented operational policies (see eclipse.org/legal/robots), the Jetty bot strictly adheres to all Disallow directives in robots.txt. It respects Crawl-Delay headers when present and will not bypass restrictions for private or restricted paths. Evidence from the project’s GitHub issue tracker confirms that the bot was specifically configured to honor exclusion rules after a community request in 2018.

🔍 Detection Indicators

The bot identifies itself with the User-Agent string “Jetty/9.4.53.v20231009” (the version corresponds to the Jetty server release used for the crawler) or more simply “JettyBot/1.0”. Additional fingerprint includes the “From” header set to [email protected] and a “Referer” header that typically points to a test page on the Eclipse infrastructure site. The bot’s requests always originate from hostnames ending in .eclipse.org and are reverse-DNS resolvable to the foundation’s IP pool.

📊 Data Usage

Collected data is used exclusively for operational monitoring: detecting broken hyperlinks, verifying SSL certificate validity, measuring response times, and ensuring that the Jetty project’s static assets are served correctly. No content is stored, indexed, or shared with third parties. The Eclipse Foundation publishes a monthly summary of crawl results via its status page (status.eclipse.org) but retains no raw page content beyond transient logs.

⚙️ Rate Limiting Policy

Even though the Jetty bot is legitimate and operated by a trusted organization, it is still rate-limited because its crawl pattern can be aggressive when scanning large sites with many pages. Threshold-based blocking (e.g., 5 requests per second from the same IP) ensures the bot does not degrade performance for human users, and the Eclipse Foundation supports such limits as a standard security practice.

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