Cloudflare Custom Error Page Crawler
ReviewCloudflare Custom Error Page Crawler is a crawler framework from Cloudflare used for Cloudflare Custom Error Page Crawler is used for Cloudflare Custom Error Page Crawler fetches customer error pages so they can be served or cached at the edge when needed.
User-Agent
Collapsify/
User-agent strings are identity signals, not proof of identity. Use Edge to compare the user-agent with IP, datacenter, behavior, path, and request history.
Verification and Detection
Verification method: Verify Cloudflare Custom Error Page Crawler by matching `Collapsify/` to Cloudflare evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
Cloudflare Custom Error Page Crawler traffic is primarily detected by the `Collapsify/` user-agent pattern; related patterns include `Collapsify; Cloudflare Collapsify; Custom Error Page Crawler`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Cloudflare infrastructure before trusting the traffic.
Handling Guidance
Use this public record as identity context, then verify source, behavior, and site impact inside Edge before creating rules.
Cloudflare Custom Error Page Crawler is used for Cloudflare Custom Error Page Crawler fetches customer error pages so they can be served or cached at the edge when needed.
Record Details
- Aliases
- Collapsify; Cloudflare Collapsify; Custom Error Page Crawler
- Type
- crawler
- Operator
- Cloudflare
- Family
- Cloudflare
- Kind
- Crawler
- Purpose
- Error Page Caching
- Identity
- Documented
- Detection confidence
- Medium
- Spoofing risk
- Cloudflare Custom Error Page Crawler Has Medium Spoofing Risk Because User Agent Strings Can Be Copied; Pair The Match With DNS, IP, Behavior, Or Operator Evidence.
- Status
- Active
- Respects robots.txt
- Unknown
- Last verified
- 2026 06 22
Robots.txt Snippet
User-agent: Collapsify/
Disallow: /
Traffic Matching
Live IP verification, reverse DNS, ASN and datacenter correlation, request history, connected-domain matches, behavioral context, and rule creation are kept inside Botcrawl Edge.
Open full record in Edge