🤖 Overview

The user-agent string Mozilla/5.0 (Windows NT 6.1; rv:7.0) Gecko/20100101 Firefox/7.0 is a legacy browser identification originally corresponding to Mozilla Firefox version 7.0, released on September 27, 2011. This user-agent is not a single bot but is commonly spoofed by a variety of legitimate automated agents, including web scraping frameworks like Scrapy (version 2.6 with default settings), the Selenium WebDriver when controlling a Firefox 7.0 binary for compatibility testing, and certain SEO audit tools. The string is also observed in traffic from historical page monitoring services such as Pingdom and GTmetrix, which reuse older Firefox user-agents to emulate real user behavior while crawling. No single commercial entity operates a bot exclusively under this string; instead, it serves as a generic identifier for automated scripts that wish to avoid modern bot detection by appearing as a low-risk, older browser. The exact version 7.0 of Firefox is now obsolete and no longer supported by Mozilla, meaning any agent claiming this identity is likely automated.

🌐 Technical Behavior

Agents using the Firefox/7.0 user-agent typically perform standard HTTP GET requests, often with an empty or generic Accept header. They may not support modern web protocols such as HTTP/2 or TLS 1.3, defaulting to HTTP/1.1 and TLS 1.2 when available. Crawl patterns vary widely because the string is used by multiple distinct tools; some exhibit high request rates of 10–50 requests per second, while others throttle to 1–2 requests per second. IP ranges cannot be tied to a single source — it originates from residential proxies, cloud providers (e.g., AWS, DigitalOcean), and even mobile carriers. Bot detection firms such as Shape Security and Imperva report that this user-agent is frequently associated with headless browser automation (e.g., Puppeteer with --user-agent overrides). The requests often lack proper HTTP_ACCEPT headers for images and stylesheets, indicating a focus on HTML content. Some instances include a Referer header set to the target domain itself, a common scraping tactic.

📋 robots.txt Compliance

Compliance with robots.txt is inconsistent because the user-agent string is not tied to a single bot with published policies. The original Firefox browser always honors robots.txt, but automated scripts spoofing this string may ignore the file entirely. Official documentation for Selenium and Scrapy does not include robots.txt enforcement by default; however, many operators configure their crawlers to respect Disallow directives. There is no evidence of a central registry or support page for this user-agent, making enforcement of rules dependent on the specific tool’s configuration. Web administrators should not assume robots.txt will be honored by traffic carrying this user-agent, as it is often used for aggressive scraping where compliance is optional.

🔍 Detection Indicators

The definitive indicator is the exact user-agent string: Mozilla/5.0 (Windows NT 6.1; rv:7.0) Gecko/20100101 Firefox/7.0. Variations may include different operating system identifiers (e.g., “Windows NT 5.1” for XP). Behavioral fingerprints include the absence of typical browser features like CSS loading (no CSS background images fetched) and lack of JavaScript execution in initial requests. The Accept-Language header may be missing or set to a single language (e.g., “en-US”). Some instances send a “DNT:1” header (Do Not Track) even though the real Firefox 7.0 did not support DNT. The requests often have a consistent time gap of exactly 1 second, suggesting a delay-controlled crawler. Security researchers at PortSwigger have documented this user-agent in the context of automated vulnerability scanners that incorrectly identify as Firefox 7.0.

📊 Data Usage

Data collected by agents using this user-agent is applied to a variety of legitimate purposes: search engine indexing (rare), competitive price monitoring, SEO analytics, content archiving, and automated application testing. Tools such as HTTrack offline browser have been known to use this string to archive websites for personal offline use. In the context of Selenium, the data is used to validate page rendering across old browsers. No single organization centralizes the collected data; instead, each operator retains the data for their own analytics or training datasets.

⚙️ Rate Limiting Policy

Because the Firefox/7.0 user-agent is frequently abused by aggressive scrapers and does not reliably respect robots.txt, a rate limit of 10 requests per minute per IP is recommended. This threshold preserves bandwidth for legitimate browsers while reducing the impact of automated agents that may inadvertently or deliberately over-crawl. The policy rationale is based on the fact that a real Firefox 7.0 browser would generate only a handful of requests per page load, not sustained bursts.

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