Overview
BLEXBot is a search crawler from WebMeUp used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Its primary user-agent pattern is BLEXBot; a representative HTTP user-agent is Mozilla/5.0 (compatible; BLEXBot/1.0; +http://webmeup-crawler.com/).
BLEXBot is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
BLEXBot is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
BLEXBot should be reviewed against site policy, source evidence, crawl rate, and requested paths before a permanent allow or block rule is created.
Identity
- User-Agent Pattern
-
BLEXBot - HTTP Agent Examples
-
Mozilla/5.0 (compatible; BLEXBot/1.0; +http://webmeup-crawler.com/) - Robots Token
- BLEXBot
- Identity Type
- Verified bot
- Evidence Method
- Verify BLEXBot by matching `BLEXBot` to WebMeUp evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
Classification
- Type
- Search
- Kind
- Crawler
- Family
- WebMeUp
- Purpose
- Indexing
Behavior and handling
- Common Use
- BLEXBot is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Detection Notes
- BLEXBot traffic is primarily detected by the `BLEXBot` user-agent pattern; a representative HTTP user-agent is `Mozilla/5.0 (compatible; BLEXBot/1.0; +http://webmeup-crawler.com/)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with WebMeUp infrastructure before trusting the traffic.
- Respects robots.txt
- No
- Spoofing Risk
- BLEXBot has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# This agent may ignore robots.txt. Use authenticated access controls or network policy when blocking is required.
Relationships
- Operator
- WebMeUp Checked 2026-06-23
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.