A zero-day warning creates two immediate questions: can an attacker reach the vulnerable feature, and does the traffic actually pass through your defenses? Before treating a quiet WAF dashboard as reassurance, verify the second question. A correctly configured application entry cannot protect requests that take another route.
This troubleshooting guide focuses on one concrete misconfiguration: the application's public DNS record still points to its origin server after SafeLine has been configured. The application works, but visitors bypass the WAF. During suspected zero-day exploitation, that mistake can leave a security owner watching the wrong evidence.
The attack concern: exploitation reaches the origin directly
An attacker targeting a newly disclosed vulnerability sends requests to the affected endpoint and varies inputs to find an exploitable behavior. Depending on the vulnerability, the objective might be unauthorized data access, command execution, or a foothold for further intrusion. Automated tooling can repeat these attempts across exposed applications and alternative hostnames.
The defender may see unusual requests in origin access logs, application errors near those requests, or unexpected activity involving the affected feature. None alone proves successful exploitation. They do establish a reason to preserve evidence and investigate the request path.
SafeLine's documented deployment model is an HTTP/HTTPS reverse proxy: it receives application traffic and forwards traffic upstream after inspection. Its application setup instructions explicitly require resolving the application's domain to the SafeLine server's IP address. If DNS still resolves to the origin, that required routing step is missing. See the official application configuration guide.
Diagnose the stale DNS record
Start with a request you can identify without sending an exploit. From an external network, request a harmless application URL with a unique query value, and record the time, hostname, and response. Locate that request in the origin's access log.
Then inspect the public DNS answers for the hostname. Check both IPv4 and IPv6 records, and compare the returned addresses with the intended WAF entry point. An old IPv6 record can preserve a bypass even when the IPv4 record has been corrected. Consider resolver caching when interpreting different answers.
The concrete fault in this scenario is straightforward: the public hostname resolves to the origin address instead of the SafeLine address. An empty attack list is only a clue, because ordinary requests need not appear as attacks. The DNS answer establishes the routing error.
Before changing DNS, check the application's SafeLine configuration. The documented Applications screen provides Domain, listening Port, an SSL option for HTTPS, and Upstream, which identifies the real application address. Confirm that these values describe the intended hostname and backend. These fields and their meanings are documented in the official setup instructions.
Correct the route and capture visible proof
Update the application's DNS records to the intended SafeLine address. After the relevant caches expire, repeat the external DNS lookup and normal application request. Verify that legitimate page loads and essential API operations still work.
Next, use an authorized test application or a controlled test window to validate inspection. SafeLine's documentation supplies common attack test cases, including a path traversal query, and identifies two observable results: a blocking page and an entry in the web console's attack list. The same guide instructs operators to click "detail" to inspect an attack. Use those documented checks rather than an unverified zero-day payload against production. See the official validation procedure.
Record the test time and requested URL. Confirm that the blocking page appears and that a corresponding attack entry is visible in the console; open its detail view and correlate the available information with your test. Together with the corrected DNS answer, these observations confirm that this tested request now reaches SafeLine and triggers inspection.
Keep the conclusion narrow. A blocked path traversal test confirms that request path and detection case. It does not prove protection against an unrelated zero-day or show that every public hostname follows the same route.
Decide what still needs containment
DNS correction does not prevent someone who knows the origin address from attempting direct access. Review origin network exposure and, where your architecture permits, restrict application ingress to the intended proxy path. Validate health checks and operational dependencies before enforcing those restrictions.
For the vulnerable feature itself, follow the software vendor's mitigation and patch guidance. If exploitation remains plausible and no reliable mitigation exists, consider temporarily disabling or isolating the feature. Preserve relevant logs and investigate possible effects on files, processes, credentials, and application data. A routing fix cannot undo an earlier compromise.
Does a successful blocking test prove the zero-day is covered?
No. It demonstrates handling of that particular test request. Assess the actual vulnerability separately, including affected versions, required privileges, exposed endpoints, and vendor guidance.
Why was the application available while the WAF showed no attacks?
In this scenario, DNS sent requests directly to the origin. Application availability confirmed that a server answered; it did not establish that traffic passed through inspection.
Which screen confirms the fix?
For the documented attack test, look for the SafeLine blocking page and the corresponding web console attack-list entry, then inspect "detail." Pair that evidence with corrected public DNS answers. The official application guide describes these validation screens.
What if suspicious activity continues after routing is corrected?
Check alternate hostnames, remaining DNS records, direct origin access, and other exposed listeners. Also investigate whether the suspicious behavior reflects an existing compromise. Continue patching and incident investigation even when the controlled WAF test succeeds.
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.