Setup
Protect a site with PingLess WAF in about five minutes: add your domain in the console, point DNS at the edge hostname, and lock down the origin.
Last updated
On this page
Setting up PingLess WAF takes about five minutes and one DNS change. You add your domain in the console, point DNS at the edge hostname you receive, and your site is protected — nothing is installed on your server.
Before you start
You need a domain you own, with access to its DNS records at your registrar or
DNS provider, and the address of your origin — the server that actually serves
your site. The base plan includes one origin and covers wildcard subdomains, so
example.com and *.example.com are protected together. WAF Pro lifts the
origin limit.
1. Add your domain in the console
Open PingLess WAF in the console and add your domain. You receive an edge hostname — the address of our edge network for your site.
2. Point DNS at the edge
At your DNS provider, replace the record for your site with a CNAME record
pointing at the edge hostname. Do the same for the wildcard record if you use
subdomains. Once the change propagates, traffic flows through the edge and
protection is on.
3. Keep the origin safe
The WAF only filters traffic that passes through it. Anyone who discovers your origin's IP address can try to reach the server directly and skip the edge entirely.
4. Verify protection
Load your site in a browser — it answers through the edge as normal. In the console, the domain shows as protected once traffic is flowing. The managed ruleset is already filtering floods, bots, and common CVE exploits; see Rules and protections for what is covered.