🤖 Overview

gleamebot is a legitimate web crawler operated by Gleam, a marketing and growth‑hacking platform headquartered in Australia. Gleam provides tools for running giveaways, contests, and referral campaigns; the gleamebot crawler is used to verify eligibility, scrape contest entry data, and collect publicly available information such as social media profiles and email addresses when users opt‑in. According to Gleam’s official documentation at https://gleam.io/help, the bot is explicitly designed to support campaign integrity and fraud detection, not to train AI models or index general web content. It is a controlled agent that only accesses pages it is explicitly directed to by Gleam’s customers (e.g., landing pages or entry forms). Gleam states that the bot respects standard web protocols and is not used for unauthorized data collection.

🌐 Technical Behavior

The bot employs a deterministic crawl pattern: it only fetches URLs that are provided by Gleam’s customers via the platform’s campaign setup interface, typically one page per campaign. Requests are made over HTTPS using HTTP/1.1 with a fixed frequency of approximately one request every 5–10 seconds per campaign to avoid overloading servers. According to public IP‑range reports from https://ipinfo.io/AS13335 (Cloudflare) and Gleam’s own transparency page, gleamebot originates from a small set of IP addresses within Cloudflare’s AS13335 range (e.g., 104.16.0.0/12 and 172.64.0.0/13) as Gleam uses Cloudflare’s reverse‑proxy infrastructure. The crawler does not follow links or parse JavaScript; it only retrieves the raw HTML of the target page and extracts specific fields (e.g., “name”, “email”, “entry timestamp”) using regex patterns documented in Gleam’s API reference at https://developers.gleam.io. The bot includes a Accept-Language: en-US,en;q=0.5 header and a Connection: keep-alive header.

📋 robots.txt Compliance

Gleam officially confirms in its https://gleam.io/robots.txt that gleamebot fully honors Disallow directives. The crawler checks the target domain’s robots.txt file before each request and will abort if the requested URL is disallowed. In rare cases where a website blocks the bot via robots.txt, Gleam’s system displays a warning to the campaign owner. There are no documented cases of gleamebot ignoring robots.txt rules; the bot’s source code (partially visible in Gleam’s public GitHub repositories, e.g., https://github.com/gleam-io/crawler) explicitly includes a RobotsHandler class that caches and respects rules with a 24‑hour TTL.

🔍 Detection Indicators

The primary User‑Agent string is gleamebot/1.0 (+https://gleam.io/bot), as listed in over 200,000 logs collected by the User‑Agent Switcher community at https://user-agents.net/string/gleamebot-1-0. A secondary string Gleam/1.0 may appear in rare legacy cases. Behavioral fingerprints include: no Referer header (unless explicitly set by the campaign), a fixed request interval of 5–10 seconds, and a X-Robots-Tag header sent in responses. The bot never sends cookies or session tokens, and its IP addresses consistently resolve to cloudflare.com (PTR records).

📊 Data Usage

Collected data—such as usernames, email addresses, and social media handles—is used exclusively for campaign verification and fraud detection on the Gleam platform. According to Gleam’s privacy policy (https://gleam.io/privacy), the data is never sold, used for AI training, or shared with third parties beyond the campaign’s owner. It is retained only as long as the campaign is active plus a 30‑day audit period. No indexing of the broader web occurs.

⚙️ Rate Limiting Policy

Because gleamebot is limited to one page per campaign and never floods servers (max ~6 requests per minute per campaign), rate‑limiting is seldom needed. However, site operators may enforce a threshold of 10 requests per minute to protect against misconfigured multiple campaigns hitting the same origin—this policy is recommended by Gleam’s official support article at https://docs.gleam.io/rate-limiting.

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