Cloudflare for Small Business. DNS, Website Protection and Why It Matters
Cloudflare is more than a website accelerator. For a small business, its DNS and web application firewall can make your site faster and harder to attack.
Cloudflare sits between your visitors and your website, and it also runs one of the largest DNS services in the world. For a small business that means two useful things: a reliable place to host your domain's DNS records, and an optional layer of protection in front of your website. Neither needs a big budget, and both can usually be set up without changing where your site is hosted.
DNS is the system that turns your domain name into the addresses your website and email depend on. If those records are wrong, missing or hijacked, your website and your email can both fail. Cloudflare's DNS service is fast, has a clear management console, and supports DNSSEC, which helps prove that DNS answers have not been tampered with. It also gives you proper access control, so you can use MFA on the account and limit who can edit records, which many registrar control panels do badly.
The next layer is the proxy. When you turn it on for a record, visitors connect to Cloudflare first, and Cloudflare passes legitimate requests to your real server. That hides the true address of your server, absorbs a lot of junk traffic, and lets Cloudflare cache images and files so pages load quicker. It also gives you DDoS protection at the network edge. Cloudflare publishes which features are on which plan, and a free plan exists, so check its current plan page for what you get.
The web application firewall, or WAF, inspects requests for known attack patterns such as attempts to exploit common website plugins or inject malicious code. You can add rules of your own, for example to block countries you never trade with, to rate limit your login page, or to challenge suspicious bots. For a WordPress site that gets hammered by login attempts, this alone can be a noticeable improvement.
A few cautions apply. Put MFA on the Cloudflare account first. Document every DNS record before you move them, including email records such as MX, SPF, DKIM and DMARC, because a missed record can break email. Do not proxy records that should not be proxied, such as mail servers. And remember that a WAF reduces risk but does not replace keeping the website itself patched.
If you would like help moving your domain to Cloudflare, or tidying up DNS that nobody has looked at for years, Dragonfly IT can take care of it with you.
