Overview
Brightbot is Bright Data’s data collection crawler and the main collection pipeline used across Bright Data products and services.
Its exact documented user agent is Brightbot 1.0, and Bright Data publishes the dedicated source subnet 82.97.199.0/24.
Brightbot is Verified from current authoritative identity documentation reviewed on 2026-08-07. The identity type is Official Documented.
Bright Data documents a separate collectors.txt control system for Brightbot. The operator’s public documentation does not confirm conventional robots.txt behavior.
Brightbot may be allowed, limited, or blocked according to the site owner’s data-collection policy after the user agent and source subnet are verified together.
Identity
- User-Agent Pattern
-
Brightbot 1.0 - Aliases
- brightbot; Brightbot
- HTTP Agent Examples
-
Brightbot 1.0 - Robots Token
- Brightbot
- Identity Type
- Officially documented
- Evidence Method
- Match `Brightbot 1.0` to the current operator documentation and corroborate the request with operator-controlled verification signals where available; User-Agent strings alone can be spoofed.
Classification
- Type
- Scraper
- Kind
- Crawler
- Family
- Bright Data
- Purpose
- Data collection
Behavior and handling
- Common Use
- Brightbot collects public web data for Bright Data products and services and uses a cache layer to reduce repeated retrievals.
- Detection Notes
- Do not identify Brightbot from a copied user-agent string alone. Match `Brightbot 1.0` and verify the documented Bright Data source subnet `82.97.199.0/24`; review request paths, rates, and collectors.txt policy separately.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Brightbot has medium spoofing risk when identified by user agent alone. Pair the exact user agent with Bright Data’s published source subnet.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# Bright Data documents collectors.txt for Brightbot-specific controls. User-agent: Brightbot Disallow: /
Relationships
- Operator
- Bright Data Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.