↓ Skip to main content
Security

Cloudflare Part 3: the free tier, and what you should do with it

Cloudflare, plainly - This article is part of a series.
Part 3: This Article
The free plan is where most personal sites start, and many never need anything else. The catch is that the useful parts are mostly switched off, or left at gentle defaults. This post lists what $0 buys, with the real limits, and then the settings I’d change on a Saturday morning, in order.
Eight tiles for the Cloudflare free plan: unmetered DDoS protection, the free managed WAF ruleset, 5 WAF custom rules, 1 rate-limiting rule per IP over 10 seconds, 10 redirect rules, 10 cache rules, Universal SSL for the apex and one level of subdomains, and Zero Trust for up to 50 users.
What the free plan includes, in numbers

Part 1 explained the front desk, and part 2 showed what it did for my domains, including what I haven’t done yet. This part is the general version, for your own domain.

Words used in this post
#

TermMeaning here
WAFWeb application firewall: rules that look at each web request and block, challenge or allow it
Managed rulesetWAF rules written and kept up to date by Cloudflare
Rate limitingBlocking a client that sends too many requests in a short time
DNSSECSignatures on DNS answers, so nobody can forge them on the way
HSTSA header telling browsers “only ever use HTTPS for this site”
CAA recordA DNS record listing which certificate authorities may issue certificates for the domain
API tokenA key for scripts, limited to the permissions you give it

What the free plan includes
#

All of these are from Cloudflare’s own documentation, as of November 2026:

FeatureFree planSource
DDoS protectionUnmetered, layers 3 to 7DDoS protection
Edge certificateUniversal SSL: apex and first-level subdomainsUniversal SSL
WAF managed rulesThe Cloudflare Free Managed Ruleset only, for “high-impact and widely exploited vulnerabilities”Managed rules
WAF custom rules5; every action except Log; no regexCustom rules
Rate limiting1 rule, counted per IP, 10-second period, 10-second blockRate limiting rules
Redirect rules10Redirects
Cache rules10Cache Rules
DNSSECYes; one click plus a record at your registrarDNSSEC
Zero Trust (Access, Tunnel, Gateway)Up to 50 users, logs kept up to 24 hoursPlans

Two things stand out. The limits are small but honest: five custom rules is plenty for a blog, and one rate-limit rule is enough to protect a login page. And there’s no trial clock: the free plan is simply the free plan.

The checklist, in order
#

The order matters. The first items protect the account that controls everything else. The last ones can break your site if you rush them.

1. Lock the account
#

  • Two-factor authentication under My Profile → Authentication. Cloudflare recommends at least two different factors: say, a security key and an authenticator app. Store the backup codes offline.
  • The same at your registrar. Whoever controls the registrar can change the nameservers and take the whole domain, mail included.
  • API tokens, never the global key. A script that edits DNS gets a token with Zone DNS Edit for one zone, an expiry date, and an IP filter if you can. “The token secret is only shown once”: put it in your password manager, not in a repository.

2. Clean up the zone
#

Go through every DNS record and delete what you can’t explain. Old subdomains pointing at old servers are doors you forgot you had. In my case, 63 records became 11.

3. Get TLS right
#

  1. SSL/TLS → Overview: Full (strict) for every proxied name with an origin. Flexible sends the second half of the trip as plain HTTP, and Full accepts any certificate. Cloudflare’s own advice is Full or Full (strict).
  2. Always Use HTTPS (SSL/TLS → Edge Certificates), so every http:// visit is redirected.
  3. Minimum TLS version. The setting is available on every plan; TLS 1.2 is a sensible floor today, and it switches off the old 1.0 and 1.1.

4. Sign the DNS
#

DNS → Settings → Enable DNSSEC, then copy the DS record it shows into your registrar’s panel. If your registrar asks for the algorithm by name, Cloudflare’s 13 is ECDSA Curve P-256 with SHA-256.

# Is DNSSEC live? A DS record at the parent, and AD=true from a validating resolver.
curl -s "https://dns.google/resolve?name=example.com&type=DS"

Do it in a quiet week. A DS record that doesn’t match the zone makes the domain fail to resolve for everyone who validates.

5. Close the email doors
#

  • A domain that sends no mail gets v=spf1 -all and _dmarc with p=reject, as GOV.UK recommends. Spammers love a domain that never complains.
  • A domain that does send mail starts DMARC at p=none with reports, then moves to quarantine and reject once the reports show only your real senders. (I’m still at p=none on samarthya.me.)

6. A few WAF rules, written from what you see
#

Start with the free managed ruleset and look at Security → Events for a week or two before writing your own. A static site gets a steady stream of WordPress scanners, and that makes an easy first rule:

Rule name:  No WordPress here
When:       (http.request.uri.path contains "/wp-login.php")
            or (http.request.uri.path contains "/xmlrpc.php")
            or (starts_with(http.request.uri.path, "/wp-admin"))
Then:       Block

Use your single rate-limiting rule on whatever is expensive or sensitive, such as a login, a search or a form endpoint, not on the whole site.

Be careful with Bot Fight Mode. It’s a single switch on the free plan, and it can also challenge tools and services you want to keep; I wrote about reading its small print first.

7. Cache on purpose
#

By default Cloudflare caches static files by extension, not HTML. One cache rule can make HTML cacheable for a site that only changes when you publish. Keep the HTML lifetime short (I use 10 minutes), and give only files with a hash in their name long lifetimes (details).

8. Last, and carefully: HSTS and CAA
#

  • HSTS tells browsers to refuse plain HTTP for up to a year. If HTTPS ever breaks, through an expired certificate, a grey-clouded record or nameservers moved away, then “your website becomes inaccessible to visitors” until the policy expires. includeSubDomains applies it to every subdomain, and preload can’t be undone quickly. Start with a short max-age on one name, and only lengthen it once you’re sure.
  • CAA records list which certificate authorities may issue for your domain. When you add any, Cloudflare adds its own CAs automatically (hidden in the dashboard), so Universal SSL keeps working. Remember to include the CA your other hosts use, such as Let’s Encrypt for an origin.

What you don’t get for free
#

So the picture is fair:

  • Only the free managed ruleset. The full Cloudflare and OWASP rulesets need a paid plan.
  • No regex in custom rules, and no logging-only action. You can’t trial a rule quietly; test it on a narrow match.
  • One rate-limit rule, counted per IP only, with a fixed 10-second window.
  • Zero Trust logs for a day, and only 50 users.

For a blog, a portfolio or a family site, none of that has mattered to me.

Takeaways
#

  • Protect the account before the site: 2FA on Cloudflare and the registrar, and scoped API tokens.
  • Delete the DNS records you can’t explain. It’s the cheapest hardening there is.
  • Full (strict), Always Use HTTPS and DNSSEC are low-risk wins. HSTS is a one-way door, so do it last.
  • Write WAF rules from what you see in Security Events, not from fear. Five rules go a long way.
  • Use the single rate-limit rule on the one endpoint that hurts most.

References
#

Next: part 4, an introduction to zero trust, and what the free Zero Trust plan can do for a household.

Author
Samarthya
Engineer, learner, tinkerer. This is my trophy shelf of everyday work and leisure.
Cloudflare, plainly - This article is part of a series.
Part 3: This Article

Related

Cloudflare Part 2: how it secured my two sites

After the blog was hacked, I had two jobs: get off the server that let it happen, and make sure whatever stayed there was hard to reach. Cloudflare did most of the second job, though not all of it. This post goes through each risk, the setting that answers it, and what’s still open. Two domains, every record with a job Part 1 covered the front desk in general. This post is about my own front desks. Earlier posts have the click-by-click detail; here I’m looking at what each step protects against.

Cloudflare Part 1: an introduction

Think of a hotel. Guests never walk straight to a room: they talk to the front desk, which checks who they are, answers what it can, and only calls up to the room when it has to. Cloudflare is a front desk for a website. This series is about what that desk does, how it protected my two domains, and what you get from it for free. Two ways to reach a site: through the front desk, or around it I’ve used Cloudflare for a month now, for samarthya.me since the blog moved after the hack and for bhanuni.in. Earlier posts showed single steps. This series puts them together, starting with the basics.

Building about.samarthya.me, part 3: Cloudflare in front

The hub lives on an old server I no longer fully trust. So it gets a receptionist: every visitor talks to Cloudflare, and only Cloudflare talks to the server. This post is about setting up that front desk, record by record. One domain, four kinds of record, one front desk Part 1 and part 2 produced the data. Before the site can be published (part 6), it needs an address, a certificate and a sensible cache.