Ki-Ki Websites and web tools

Cloudflare security reviews

This page exists for the people who ask what do you really do in Cloudflare.

If you just want the outcome, the summary is simple. Good visitors get through smoothly, junk traffic is filtered, suspicious visitors are logged and challenged.

Who this page is for

  • You see real rule patterns and worker ideas
  • You see why they exist in the first place
  • You get links to live monitoring write ups
  • You have something concrete to show internally

Examples of rules and edge logic

These are simplified patterns based on real work. Values change per client. The idea stays the same.

Firewall rulecraft

Tight control over sensitive routes like logins and admin tools.

(http.request.uri.path contains "/wp-login.php"

 and ip.geoip.country ne "GB")

Plain English: if someone tries to reach the WordPress login from outside the country you actually work in, they get challenged or blocked. Real staff use known locations or a VPN you trust.

Bot filtering

Respect good crawlers, slow down the noise.

if (cf.bot_management.score <= 20)

  action = ManagedChallenge

Good bots pass, low quality scraping tools usually do not bother.

Honeypots and canary routes

Hidden paths that only scanners find.

(http.request.uri.path eq "/.well-known/scan"

 or http.request.uri.path eq "/old-admin")

Plain English: if anything touches these routes, it is not a normal visitor. We log it, alert if needed, and can block that source earlier next time.

Workers and edge responses

Let the edge deal with junk instead of your server.

if (country not in ["GB","IE"]) {

  return new Response("Not available in your region", {

    status: 403

  });

}

Plain English: if your service is meant only for people in certain areas, requests from elsewhere never reach your hosting. They are handled at the edge with a clear response.

The non technical version

What I do for your site

I sit your site behind a smart front gate. Real visitors get in quickly. Suspicious requests are slowed, challenged, or blocked. You get a clear record of what happened.

Why it is worth doing

Most small sites receive more junk than genuine traffic. Without filtering, your analytics lie to you, your hosting works harder than it should, and problems are harder to spot.

What you can show internally

You can show a short monthly summary. For example: how many requests were blocked, where they came from, which rules did the work, and what changed as a result.

How this turns into your own stack

If we work together, I take this pattern and scale it to your size and risk. No generic preset. Just rules that make sense for who you are and who might take an interest in you.

  • For SMEs

    Keeps sites and logins calm, removes a lot of junk from contact forms, and gives you reliable analytics for marketing spend.

If your logs or instincts say something is off

Tell me what you are seeing, even if it feels vague. Odd referrers, strange spikes, repeated visits from somewhere that does not make sense. I can usually tell you quickly whether it is noise or worth acting on.

Your details are used only to reply and schedule any call. No mailing lists, no resale of data.