Site Shield·Flagship
Turn the scanners hitting your static site into attributed, blocked adversaries — without adding a single script to the pages real visitors load.
For: Executives, founders, consultants, small teams on Cloudflare Pages
- 0 scripts added to your real pages
- No added latency for real visitors — the Worker only runs on trap paths
- Strict CSP left exactly as it is
See how it works →Decoy subdomains
Give subdomain enumeration exactly what it’s looking for: a staging environment that looks forgotten, answers like a real app, and reports everything back.
For: SaaS teams, compliance platforms, anyone with a public product domain
- Bait hostnames that read as real infrastructure
- No inbound ports — Cloudflare Tunnel only
- Real client IP via Cf-Connecting-Ip, trusted only from the tunnel peer
See how it works →Canary files
The attacker leaves with a file. The file keeps reporting. Fake credentials that trip an alert the moment anyone tries to use them.
For: Security teams who want a signal that outlives the session
- Decoy .env, .zip, .sql and .pdf files
- Per-session canary tokens, so a trip maps back to who took the file
- Alerts that fire after the session ends
See how it works →Shared enforcement
Trap the attacker on one domain and block them on all of them. Enforcement lands as account-level Cloudflare rules, not per-site config.
For: MSPs, MSSPs, fractional CISOs, anyone running a portfolio of domains
- One block, enforced on every domain in the Cloudflare account
- Low-value domains turned into early-warning sensors for high-value ones
- One sensor and one console across the portfolio
See how it works →