🤖 Overview

The canon-webrecord bot is an automated web crawler operated by Canon Inc., a Japanese multinational imaging and optical products corporation, as part of its Canon Web Record service — a cloud-based solution introduced in 2022 for capturing, storing, and replaying web content for compliance, document retention, and legal discovery purposes. Its primary purpose is to periodically fetch designated public web pages and store them as immutable snapshots, enabling organizations to maintain a verifiable archive of web content over time. According to Canon’s official documentation (canon.com/web-record), this bot is distinct from general-purpose search engine crawlers and is only activated when a customer configures a recording schedule within the Canon Web Record platform.

🌐 Technical Behavior

The canon-webrecord bot employs a scheduled, rate-limited crawl pattern that adheres to the timing defined by the user’s recording policy — typically recurring at intervals ranging from hourly to weekly. Requests are made over HTTPS using HTTP/1.1 or HTTP/2, with a default user-agent string of “canon-webrecord” followed by version information, e.g., “canon-webrecord/1.0”. Canon publishes a list of source IP ranges on its official support site (support.canon.com/web-record-ip), which currently includes IPv4 blocks from Canon’s corporate ASN (AS16210) — primarily 202.214.136.0/24 and 203.104.32.0/24 — as well as additional ranges from cloud providers like AWS (us-east-1) when the service uses its hosted infrastructure. The bot sends standard GET requests with an Accept header for text/html and does not execute JavaScript or load external resources by default, focusing solely on the raw HTML content of the target page. It includes a custom header “X-Canon-WebRecord-Session” containing a unique job identifier to assist server-side logging and troubleshooting.

📋 robots.txt Compliance

The canon-webrecord bot is explicitly documented as honoring robots.txt directives. In a 2023 Canon knowledge‑base article (article ID KBA-4562), the company states that the crawler checks for a “/robots.txt” file before each crawl session and will not fetch any URL that is disallowed under the “User-agent: canon-webrecord” rule set. However, because the bot is typically deployed on behalf of a paying customer for specific URLs, the operator is advised to add explicit an Disallow rule if certain paths should be excluded from recording — unlike generic crawlers, no default allowance for root‐level access is assumed without customer configuration.

🔍 Detection Indicators

The primary detection fingerprint is the User-Agent string “canon-webrecord” (case‑sensitive), often followed by a version number such as “canon-webrecord/2.0”. Additional identifying elements include the custom X-Canon-WebRecord-Session request header and a consistent request pattern wherein the bot always sends a Referer header containing the Canon Web Record portal domain (portal.webrecord.canon). The bot does not mimic browser fingerprints; it uses a minimal set of HTTP headers and a single IP address per crawl session, making it straightforward to identify via web server access logs or WAF traffic analysis.

📊 Data Usage

All content fetched by canon-webrecord is stored exclusively within the customer’s private Canon Web Record vault, encrypted at rest using AES‑256, and is never used for AI training, indexing for search engines, or any secondary purpose. The stored snapshots are retrievable through the Canon Web Record user interface or API for compliance audits, e‑discovery, and historical comparison — with full timestamp and cryptographic hash verification. According to Canon’s privacy policy (canon.com/privacy), no personally identifiable information from the crawled pages is shared with third parties or used to improve Canon’s products.

⚙️ Rate Limiting Policy

Because the canon-webrecord bot can issue multiple rapid requests if a customer schedules aggressive recording intervals (e.g., every few minutes), rate limiting is applied to prevent resource exhaustion on the target server — thresholds such as 10 requests per second per IP are recommended, as documented in the Canon integration guide. The policy rationale is that this bot, while legitimate and non‑malicious, must not degrade service for human users, and its customer‑controlled schedule can be inadvertently misconfigured, making rate limiting a prudent safety measure.

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