Cloudflare edge signals were detected, but the homepage served cleanly to a plain HTTP client during this snapshot; no active challenge was observed. Difficulty remains per-URL, so deep pages — profiles, listings, search — can behave differently.
The snapshot detected Cloudflare as an edge-security layer. This result describes only the tested homepage response, which was not actively challenged from that vantage point.
Typical access
Plain HTTP
Detected vendors
Evidence
Detection confidence: high · vendor present but served clean (passive edge, not an active challenge)
Homepage-level, datacenter-IP snapshot, June 13, 2026.
This is a homepage-level snapshot and can be inaccurate or out of date — anti-bot vendors update their models continuously, deep pages are usually more protected than the homepage, and difficulty is IP-sensitive: a site can read differently from a clean vs a flagged IP and even flip over time. Treat it as a directional signal, not a guarantee.
The homepage is the open front door. On a crypto site the valuable pages behave differently — here's the plan to characterise pancakeswap.finance before you build.
Quote / ticker
JS renderOpen but JS-rendered; numbers load via XHR.
Screener / search
rate-limitedOpen but rate-limited.
Find a real deep URL cheaply from the site’s robots.txt and sitemap.xml, then run each through the anti-bot checker. This is an advisory based on the category and pancakeswap.finance’s homepage result — detect the wall, never try to pass a login.