Spot the attackers. Keep them out.
See who is probing your site for weak spots, and stop them before they reach it.
- 203.0.113.42GET /.envAttack path · 404
- 203.0.113.77GET /wp-login.phpBlocked · 403
- 198.51.100.5GET /.git/configAttack path · 404
- 198.51.100.19GET /xmlrpc.phpBlocked · 403
- 203.0.113.88GET /adminImpostor · 403
- Review 1 campaign of 9 senders
- Keep Attack paths on
- Add 2 team addresses to Trusted
Every public site gets probed. You just rarely see it.
Automated tools ask for your .env, your .git/config, your wp-config.php and admin pages, thousands of times a month. Sill groups them by sender and shows you what they tried.
17 attack types, recognised as they happen.
- Secret files
GET /.env - Admin login floods
/wp-login.php × 40 - SQL injection
?id=1' OR 1=1 - Webshell probes
/uploads/x.php - Path traversal
/../../etc/passwd - Fake crawlers
UA: 'Googlebot' - Vulnerable plugins
/revslider/release_log.txt - Source leaks
/.git/config
- Frankfurt203.0.113.42Hosting · HetznerEnv + wp-config scan (12 paths)Seen on 14 sites
- Ashburn203.0.113.77Hosting · DigitalOceanWordPress admin login burstSeen on 6 sites
- Paris198.51.100.5Cloud · OVH.git/config, backup zipsFirst time
- Amsterdam198.51.100.19Hosting · LinodeWebshell upload probeSeen on 3 sites
- Singapore198.51.100.33Cloud · AlibabaSQL injection on searchSeen on 9 sites
- São Paulo203.0.113.88Mobile · VivoAdmin page, UA: 'Googlebot'First time
Two switches do the work.
You decide what gets blocked. Sill does not block a sender on its own unless you ask it to. Seeing who probes your site is on every plan. Blocking is on the Protect plan and needs your site on Cloudflare. See pricing.
Blocking
Stop specific senders at Cloudflare, before they reach your site.
- Who it stops
- Addresses or ranges on your block list.
- What they get
- An Access denied page, before they reach your site.
- Never blocked
- Verified crawlers, Cloudflare's own network, privacy relays, and addresses on your trusted list.
Attack paths
Refuse the file paths attackers probe for, from anyone.
- What it refuses
- Paths attackers ask for: .env files, git folders, backups, admin scripts. Plus your own list.
- What they get
- A plain Not found page, as if the file isn't there.
- Who it applies to
- Every sender, crawlers included.
Coordinated attacks, grouped.
When several addresses probe the same paths together, Sill groups them into one campaign you can block in a single step.
/.env/.git/config/wp-login.php/wp-content/uploads/.*\.php/admin/debug/backup.zip/config.old+3
- Frankfurt
203.0.113.42Hosting · Hetzner12 min agoBlocked - Ashburn
203.0.113.77Hosting · DigitalOcean18 min agoBlocked - Paris
198.51.100.5Cloud · OVH22 min agoBlocked - Amsterdam
198.51.100.19Hosting · Linode31 min agoBlocked - Singapore
198.51.100.33Cloud · Alibaba46 min agoBlocked - Mountain View
203.0.113.88Google LLC14 min agoVerified crawler - Berlin
198.51.100.142Office IP27 min agoOn your trusted list - Dallas
203.0.113.9Hosting · own origin33 min agoYour own server - São Paulo
198.51.100.202Residential · Vivo51 min agoResidential - +3 more
Fair questions.
Which installs can see attack requests and block senders?
The Cloudflare Worker sees attack requests, refuses attack paths and blocks senders. The WordPress plugin sees attack requests and refuses attack paths, but does not block senders. The script tag and the Shopify app record visits only.
What does Sill never block?
Verified search and AI crawlers, Cloudflare's own network, privacy relays like iCloud Private Relay, and addresses on your trusted list. Sill asks you to confirm before you block the address you are using right now.
Is this a web application firewall?
No. Sill shows you who is probing your site and lets you shut them out at your Cloudflare Worker. Your existing firewall keeps running.
How long are addresses kept?
30 days.
Who on my team can see the address behind a visit?
Owners, admins and reviewers can, for the last 30 days. Viewers, Sill support sessions and agencies acting in a client account cannot. Every reveal and every full-address search goes to the audit log.
Want to see how we back up what we do?
The signed audit records, the public key, the in-browser verifier and our red team against our own rules live in the Trust centre.