Skip to content

Protect your site

Every public store gets probed: automated tools ask for password files, try old admin logins and test for known holes, thousands of times a month. Sill shows you who is doing it and what they tried, and lets you stop them before the request reaches your server, without blocking real customers or the AI agents you want.

Protection works on top of the visit tracking you already have. You decide what gets blocked; Sill never blocks a sender on its own unless you ask it to. Everything lives under Security in the top navigation, which opens on a summary of the period.

SwitchWhat it does
BlockingStops the addresses on your block list from opening any page. They get Access denied from your Cloudflare Worker.
Attack pathsRefuses requests for attack paths only, such as /.env, from anyone, with a plain not found. No address is blocked: the same visitor can still open every normal page.

Most sites should turn on both. Blocking stops a sender you want gone; attack paths stops automated probing, whoever sends it.

JobWherePage
See what happened this period and what to do nextSecurity → SummarySecurity summary
Spot attacks and tell you who sent themSecurity → AttackersAttack detection
Block one sender’s addressThe sender’s panel, the Block buttonBlock a sender
Refuse requests for secret files, whoever sends themSecurity → PathsAttack paths
Stop a group of addresses working togetherA campaign under Security → AttackersCampaigns
Keep your own tools and partners out of itTrust this address, Ignore for 30 daysTrusted and ignored senders
Catch bots using a known agent’s name, and disguised scannersMismatch rows, Unknown scannerImpostors and scanners

Sill can only see, and stop, requests that pass through it. What you get depends on how Sill is installed on your site; see What each install covers.

Script tag or Shopify appWordPress pluginCloudflare Worker
Records visitsYesYesYes
Sees attack requests (files such as /.env, admin pages, injection attempts)No. These requests never load a page, so the script never runs.YesYes
Shows the sender’s addressNoYesYes
Refuses attack pathsNoYes, plugin 1.10 or newerYes, Worker 1.10 or newer
Blocks addressesNoNoYes, Worker 1.8 or newer

The Cloudflare Worker covers your main domain and its www. address. Requests to other subdomains don’t pass through it.

Visitor addresses are kept for 30 days.

Owners and admins can also turn on both switches from the WHAT TO DO NEXT list on the Security summary.

With the Cloudflare Worker installed:

  1. Attack paths. Open Security → Paths. Watch the count of requests it would have refused for a few days, then click Turn on attack paths. This stops most automated probing on its own. See Attack paths.
  2. Blocking. On Security → Blocking, click Turn on blocking so the addresses you block are actually refused. See Turn blocking on.
  3. Trusted addresses. Mark your uptime monitor, payment provider callbacks or office network as trusted — from their sender panel, or by hand under Security → Trusted — so they never raise alerts and can never be blocked. See Trusted and ignored senders.

On a WordPress plugin install you can turn on attack paths (step 1); address blocking needs the Worker.

  • Verified crawlers such as Googlebot and Bingbot, when Sill has confirmed them.
  • Cloudflare’s own network and privacy relays such as iCloud Private Relay, which many real people share.
  • Addresses on your trusted list.
  • Your own servers, found in your domain’s DNS records, when a campaign is auto-blocked.

Sill asks you to confirm before you block the address you are using right now.