Cloudflare first: the shield in front of every site we host
Every site we host sits behind Cloudflare. It filters out attacks and unwanted bots before they reach your server, speeds up page loads worldwide, and only works as protection if the server behind it can't be reached directly.
Introduction
Part 4 of 5 in Secure by Design, our series on how we build, host and maintain websites that stay stable and secure.
Before a visitor, a search engine or an attacker reaches one of our sites, their request passes through Cloudflare's global network first. We set this up on every site from day one, because it makes the site both safer and faster.
What does Cloudflare do for a website?
Cloudflare sits between the internet and your server and does two jobs. It's a web application firewall (WAF) that inspects every request and blocks the malicious ones, and it's a content delivery network (CDN) that serves your site from locations close to your visitors.
Because all traffic arrives through Cloudflare, attacks are filtered out before they reach your server, including large floods of traffic designed to knock a site offline. Your server only deals with the requests worth answering.
Custom firewall rules, built from experience
Cloudflare's managed rules block known attack patterns out of the box. On top of those, we add our own rules, based on what we see across the sites we manage:
- Blocking known scanned paths: Automated scanners constantly probe websites for common weak points: old admin pages, leftover install scripts, backup files and configuration files. We block those paths outright, so the scanner gets nothing back.
- Blocking file types where they don't belong: A request for a .php file inside an uploads folder has no legitimate reason to exist. We block file types in places they should never appear, which rules out a whole category of attack.
- Rate limiting: If a single source starts hammering a login page or a form, Cloudflare slows it down or blocks it. That protects against password-guessing attacks and stops one bad actor slowing the site for everyone else.
- Locking down admin areas: Where it suits the client, we restrict the site's administrative and login pages to an approved list of IP addresses, such as your office network. Anyone else is blocked before the login page even loads, so there's no login form to attack.
Limiting what bots can learn about your site
Most attacks today start with an automated scan. Bots sweep the internet looking for sites running a specific vulnerable version of WordPress, a plugin or a framework, and the first thing they try to do is work out what your site is built on. So we make that as hard as possible.
- Hiding the tell-tale files. Many sites accidentally expose files that give away exactly what they're running: plugin readme files that list version numbers, configuration and environment files, backups, and version-control folders. We block requests for these, so a scanner can't use them to match your site against a list of known vulnerabilities.
- Not advertising your software versions. Many shared hosting providers announce the exact PHP version a site runs in a header sent with every page, called X-Powered-By. If that header says PHP 7.4, which stopped receiving security fixes in November 2022, an attacker knows exactly which known weaknesses to try. Our hosting doesn't send this information at all. If your site is on a host that does, Cloudflare can strip the header out automatically. Hiding the version doesn't fix outdated software, but it stops you being an easy match.
- Blocking automated traffic. Cloudflare can tell the difference between real visitors and most automated tools. Traffic that behaves like a scanner or a scraper is challenged or blocked, while legitimate crawlers such as search engines are still let through.
When a new vulnerability is announced, attackers start with the sites they already know are running the affected version. A site that hasn't advertised its versions is far less likely to be on that list. We cover why that window matters so much in how AI is speeding up attacks.
Protected before the patch existed
In our last article we covered php2shell, two critical flaws in PHP itself (CVE-2026-109618 and CVE-2026-109619) that can let an attacker run their own code on a server by sending specially crafted requests. Cloudflare had rules blocking the attack live at 1:02pm (Brisbane time) on 21 October, about nine hours before the flaws were made public. Every site behind Cloudflare's firewall, including those on its free plan, was protected before most site owners knew there was a problem.
That doesn't replace patching. The flaw is in PHP, so the only real fix is upgrading PHP, which was rolled out to our hosting within hours of the release. Two days later a related flaw turned up (CVE-2026-115560) that the new PHP releases didn't fully fix. Cloudflare's rules block that one too for most setups while a fix is on its way.
Cloudflare is also testing its own protection in public. It's running an open capture the flag challenge where security researchers are rewarded for finding a way past its php2shell rules. Cloudflare says those reports have already led to stronger php2shell rules and new detections.
The rise of AI traffic, and what it costs you
A growing share of the visitors to your website aren't people. According to Cloudflare, 2026 is the first year more than half of internet traffic wasn't human, and Cloudflare Radar shows the live split between people and bots.
Every one of those requests uses your server's resources, which can slow your site for real customers or push you onto a bigger, more expensive hosting plan. Because every request reaches Cloudflare first, unwanted bots are stopped there and your server only spends its resources on your actual customers. We choose with you which AI crawlers to allow, because some of them power the AI search tools your customers use to find businesses like yours.
A safety net for third-party code
Many websites load JavaScript straight from outside services, so if one of those services is compromised, malicious code runs on your site without anyone touching it. That's what happened in June 2024, when polyfill.io, used by nearly 4% of websites according to Cloudflare, was taken over and began redirecting visitors to betting sites. Cloudflare automatically swapped links to it for a safe copy, and we switch that protection on for the sites we manage. The affected code still gets replaced through our reviewed process, but the swap keeps visitors safe in the meantime. We look at why upstream code can't always be trusted in when the update itself is the attack.
Can attackers bypass Cloudflare?
They can if the server behind it isn't locked down. Cloudflare protects the traffic that comes through Cloudflare. If an attacker finds the real IP address of your server, which can leak through old DNS records, email headers or historical lookup services, they can send requests straight to it and skip Cloudflare entirely. At that point, the firewall rules, bot blocking and rate limiting described above are doing nothing.
Closing that gap means the server itself has to refuse any connection that didn't come through Cloudflare. That can be done with a firewall that only accepts Cloudflare's addresses, or more strongly with mutual TLS (mTLS), where Cloudflare and the server each prove their identity with a certificate before any connection is accepted.
Our Enterprise-grade hosting uses mTLS between Cloudflare and our servers. Even if someone discovers a server's address, a request that doesn't carry Cloudflare's certificate is turned away.
Getting ready for quantum computing
Some attackers are already collecting encrypted data and storing it, planning to decrypt it once quantum computers are powerful enough to break today's encryption. It's known as "harvest now, decrypt later", and it means sensitive data sent today could be exposed years from now. Post-quantum encryption is designed to withstand this. It's built on TLS 1.3, the latest version of the protocol that encrypts web traffic, and our hosting already runs TLS 1.3, so the groundwork for post-quantum encryption is in place.
Speed improvements built in
- Caching HTML on the edge. For pages that are the same for every visitor, we cache the whole page in Cloudflare's data centres around the world, known as "the edge". If your server is in Australia and someone visits from the USA, they get the page from a nearby US data centre instead of waiting for it to come from Australia.
- Automatic image optimisation. Images are compressed and served in modern formats automatically, so pages load faster, especially on mobile, without anyone resizing files by hand.
- HTTP/3. The newest version of the protocol browsers use to load websites. It connects faster and copes better with patchy connections, so pages load quicker on mobile networks and public wifi.
- Early Hints and Speed Brain. Cloudflare tells the browser what a page will need before the page arrives, and can start loading the page a visitor is likely to click next before they click it.
What this means for your business
- Attacks, scanners and unwanted bots are filtered out before they reach your website
- New vulnerabilities can be blocked at Cloudflare before a patch is even released
- Login pages and admin areas are protected from password-guessing attempts
- There's no back door around the protection, and the groundwork for post-quantum encryption is in place
- Pages and images load faster for visitors, wherever they are
- You're not paying for server resources to serve traffic you don't want
Cloudflare as the outer layer
Cloudflare is our first line of defence. Behind it, every site runs on pinned, reviewed code, on Enterprise-grade hosting with a read-only filesystem, and is kept current as new vulnerabilities are disclosed. In our next article (coming soon), we bring all of it together.
Frequently asked questions
Do I need Cloudflare for my website?
Most business websites benefit from it. Cloudflare filters out attacks and unwanted bots before they reach your server, and serves cached pages from data centres close to your visitors, which makes the site faster.
I've never heard of Cloudflare. Can I trust it?
Yes. Even if you haven't heard of it, you've almost certainly used it. As of October 2026, W3Techs reports that Cloudflare is used by 26.3% of all websites, about one in four, and by 85.2% of the websites that use a service like it. It's a publicly listed company running data centres in 348 cities around the world, including seven Australian cities from Brisbane to Perth.
I use Cloudflare. Can someone bypass my WAF by going directly to my server?
They can if your server still accepts connections from anywhere. If an attacker finds your server's real IP address, they can skip Cloudflare entirely and your firewall rules do nothing. Check with your hosting provider that your server only accepts traffic from Cloudflare, ideally using mutual TLS (mTLS). Our Enterprise-grade hosting does this as standard.
Does Cloudflare slow down a website?
No, it usually makes it faster. Cached pages are served from a Cloudflare data centre near each visitor, and features like HTTP/3 and Early Hints speed up loading further.
Should I block AI crawlers?
It depends on your business. Blocking AI training crawlers saves server resources, but some AI crawlers power the AI search tools people use to find businesses, so blocking all of them can reduce your visibility. A selective approach usually works best.
How do I hide my PHP version from attackers?
Many hosts reveal the PHP version in a header called X-Powered-By, and Cloudflare can remove it automatically with a built-in setting. Hiding the version doesn't replace updating, though: an outdated PHP version still needs upgrading.
If my site is behind Cloudflare, do I still need to update PHP?
Yes. Cloudflare can block known attacks against a vulnerability, sometimes before it's even announced, as it did with php2shell in October 2026. But the flaw is still in your server's PHP, and a new way around the firewall rules could turn up at any time. Cloudflare buys you time to patch; it doesn't replace patching.