How ClientSignal Works
Built with rigorous security and isolation from the ground up: verified domain ownership, isolated headless browsers, and non-destructive synthetic journeys.
Step 1: Domain Authorization & Verification
Before any active browser tests are dispatched, our system requires proof of domain ownership or authorized administrative control. You verify domains via a simple DNS TXT record or a secure verification file.
This safeguard ensures synthetic tests are only performed on web properties your agency has explicit permission to manage.
Step 2: Safe Synthetic Journey Configuration
You configure the specific form fields and supply test parameters. You also define a dedicated test destination (such as a staging email inbox or test webhook endpoint).
Step 3: Isolated Browser Execution & SSRF Protection
Tests run in isolated, ephemeral container runners. Every target URL is validated against strict Server-Side Request Forgery (SSRF) rules to block loopback addresses, private IP subnets, and cloud metadata endpoints.
Monitored HTML and form elements are treated strictly as untrusted data, ensuring hostile external scripts never execute within the ClientSignal application.
Step 4: Confirmed Incident Escalation & Client Reports
If an issue occurs, ClientSignal re-checks the endpoint to confirm whether the failure is transient or real. Confirmed failures immediately alert your agency team via Slack, email, or webhook with full diagnostic logs.
At month-end, export branded reliability summaries to show clients the uptime, speed, and continuous form testing performed under their retainer.