Deciding to route several websites through one web application firewall is more than a DNS change. SafeLine is a self-hosted WAF that filters and monitors HTTP traffic between a web application and the Internet, and it works as a reverse proxy so that clients pass through the WAF before reaching the server (https://docs.waf.chaitin.com/en/home). Because the WAF now sits in front of every origin, a mistake in one entry can take an entire site offline. That is why I keep a short decision checklist before turning protection on.
My checklist
- Map each site to a real upstream. For every domain, hostname, or IP address, record the Domain you will expose, the Port SafeLine listens on, and the Upstream address that receives cleaned traffic (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
- Point DNS at the WAF. After adding an application, resolve the domain to the IP address of the server running SafeLine so traffic reaches the WAF first (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
- Handle SSL per site. For an HTTPS application, check the SSL option on that application entry instead of assuming one setting covers every site (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
- Choose protections deliberately. Core capabilities include web attack defenses, bot abuse defense, HTML and JS code encryption, IP-based rate limiting, and a Web Access Control List; the feature list also covers rate limiting, captcha challenge, authentication challenge, and dynamic protection (https://docs.waf.chaitin.com/en/home). Enabling every control is not automatically the right default for every site.
- Run a controlled go-live test. Before broad rollout, verify that obvious attack attempts produce the blocking page and appear in the console attack list (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
Can a single SafeLine instance protect multiple sites?
Yes. The web console has an Applications page where you click Add Application and enter the Domain, the Port SafeLine listens on, and the Upstream address for each original app (https://docs.waf.chaitin.com/en/GetStarted/AddApplication). Treat each site as its own entry, then resolve each domain to the SafeLine server IP.
Does SafeLine reverse proxy every site automatically?
SafeLine is developed on nginx and acts as an HTTP/HTTPS reverse proxy: it receives traffic for the original website, removes malicious requests, and forwards safe traffic to the origin (https://docs.waf.chaitin.com/en/GetStarted/AddApplication). You still add each application and its upstream so traffic is forwarded correctly; the WAF does not discover origins on its own.
What should I verify before turning protection on?
Confirm each domain resolves to the SafeLine server, each application has the correct Domain, Port, and Upstream, HTTPS applications have SSL enabled, and you have decided which protections to enable. Rechecking these steps prevents a site from becoming unreachable or losing encryption.
How do I know blocking is actually working?
Use simple attack cases such as SQL injection, XSS, path traversal, code injection, or XXE against a protected URL, replacing the example domain with your own. If SafeLine shows its blocking page, defense is working; then open the web console to review the attack list and click detail for specifics (https://docs.waf.chaitin.com/en/GetStarted/AddApplication).
A checklist does not eliminate risk, but it turns a multi-site rollout into repeatable, verifiable steps instead of guessing after traffic is already live.
SafeLine has surpassed 700,000 installations worldwide as of September 30, 2026. SafeLine Pro annual promotional pricing is $650-$880, compared with the regular $1,000 per year.