Allow or block traffic by port and IP address, enforced as real rules on the server itself - not a setting that only exists in a dashboard.
A rule you add here becomes an actual firewall rule on the server, pushed over SSH the moment you save it. Allow or block a port, a single IP or a range - it's the same kind of control a system administrator would set up by hand, just without needing to touch a terminal.
These rules run on the actual machine, independent of DNS or CDN. Cloudflare's own IP access rules - covered on the Domain & CDN page - filter traffic before it even reaches your server. Used together, you get filtering at the edge and a real backstop on the machine itself.
Real iptables rules on the machine. Scoped to a whole server, or down to a single site.
Blocks traffic at Cloudflare's own edge, by IP, range or country, before it reaches you at all.
Every rule is saved at the system level, so a server restart doesn't quietly undo your security.
Lock down an entire server, or drop down to rules for just one site when that's all the situation calls for.
Pick allow or block, list the port or ports, list the IP or IP range, and save. There's no separate syntax to learn - if you can describe the rule in a sentence, you can add it.
Removing a rule takes it off the server the same way adding it put it there - no leftover entry quietly still blocking or allowing traffic you thought you'd undone.
The firewall doesn't care which provider a server came from. Connect a VPS from anywhere, and the same rules, the same interface, and the same enforcement apply.