---
title: "Discussion on \"Cloudflare Free Plan Security — The Exact Settings I Run on My Own Site\" | Hashnode"
description: "Discussion on \"Cloudflare Free Plan Security — The Exact Settings I Run on My Own Site\". Cloudflare free plan security with real dashboard screenshots: Full (Strict), HSTS, five WAF rules, and the switches I leave off on purpose."
url: "https://hashnode.com/posts/cloudflare-free-plan-security-the-exact-settings-i-run-on-my-own-site/6ad6512ae27f24e234aeb0be"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Cloudflare Free Plan Security — The Exact Settings I Run on My Own Site](https://quabin.hashnode.dev/cloudflare-free-plan-security-the-exact-settings-i-run-on-my-own-site?utm_source=hashnode&utm_medium=feed)

Cloudflare free plan security with real dashboard screenshots: Full (Strict), HSTS, five WAF rules, and the switches I leave off on purpose.

Oct 19 · 14 min read · quabin.hashnode.dev  
Read the article

-   [#cloudflaresecurity](https://hashnode.com/tag/cloudflaresecurity)
-   [#wordpress](https://hashnode.com/tag/wordpress)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Daanial Farrukh](https://hashnode.com/@daanial)

@daanial

  
[View profile](https://hashnode.com/@daanial)

Field notes from a presales solutions architect

Cloud presales architect — anonymized war stories and frameworks on cloud architecture, security, and the trade-offs that shape real systems.

## Responses 4

Markdown supported · ⌘↵ to post

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Oct 21](https://hashnode.com/posts/cloudflare-free-plan-security-the-exact-settings-i-run-on-my-own-site/6ad6512ae27f24e234aeb0be/comment/6ad82b6659c70499e181083a)

The honesty about free-plan rate limiting being a speed bump, not a lock, is the part most guides skip. And proving each rule with a curl command instead of trusting the dashboard is exactly the habit that separates a setup from a posture.

[Daanial Farrukh](https://hashnode.com/@daanial)

[Oct 21](https://hashnode.com/posts/cloudflare-free-plan-security-the-exact-settings-i-run-on-my-own-site/6ad6512ae27f24e234aeb0be/comment/6ad82b6659c70499e181083a#reply-6ad86f49b7abc8958ad98041)

Thanks, Rishabh. That was the point of the article. The dashboard tells you a rule exists. Only a curl test tells you it works. On the free plan, rate limiting slows a bot down but does not stop it, so the WAF rules and origin lockdown do the real work. Glad it was useful.

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Oct 21](https://hashnode.com/posts/cloudflare-free-plan-security-the-exact-settings-i-run-on-my-own-site/6ad6512ae27f24e234aeb0be/comment/6ad82b6659c70499e181083a#reply-6ad8a84b37fa8a804ee8c68d)

Fair point on the WAF rules doing the real work. One cheap trick worth adding: pair the curl checks with Security > Events filtered by blocked, so you can see exactly which rule fired per request. It closes the loop between the dashboard and the terminal.

[Daanial Farrukh](https://hashnode.com/@daanial)

[Nov 8](https://hashnode.com/posts/cloudflare-free-plan-security-the-exact-settings-i-run-on-my-own-site/6ad6512ae27f24e234aeb0be/comment/6ad82b6659c70499e181083a#reply-6af0bc8212e8e04dbae092b7)

Good tip, thanks, the Events log and the curl test confirm each other.
