Proxy Connectivity Testing
Verify reachability, exit IP, TLS and latency for HTTP, HTTPS and SOCKS5 proxies before a run.
Authorized testing only · browser QA
Test traffic. Validate campaigns.
Test traffic. Validate campaigns.
Get clear results.
Run controlled website tests, validate proxy connectivity, inspect landing-page behavior, and monitor campaign quality from one unified dashboard.
Authorized targets only. Bounded concurrency. Every session audited.
Test sessions
12,840
last 14 days · sample
Passed checks
9,126
71% pass rate
Blocked
2,544
challenge / 403
Avg response
412 ms
p95 tracked per job
Live results5 of 1,284
PASS
acme-staging.test/landing/spring
200
318 ms
BLOCKED
acme-staging.test/checkout
200
1240 ms
FAIL
acme-staging.test/api/health
0
20000 ms
PASS
docs.acme-staging.test/quickstart
200
286 ms
BLOCKED
acme-staging.test/assets/app.js
403
190 ms
Outcomes14d
Figures above are fixed sample data for layout demonstration — not customer results.
Capabilities
Everything you need to trust a deployment
Eight focused tools that answer one question: does this page behave the way it should for the people who visit it?
Landing Page Validation
Confirm status codes, titles, redirects and blocking interstitials on pages you deploy.
Campaign QA
Confirm that QA markers and ad slots render on pages you own or are authorized to test.
HTTP Status Monitoring
Track 2xx, 4xx and 5xx distributions across rendered sessions and catch regressions between deploys.
Session Diagnostics
Inspect per-session latency, the proxy used, the failure category and the exact error text.
Real-Time Analytics
Pass rate, p95 latency and error breakdowns across the last fourteen days.
Exportable Reports
Download a CSV of any filtered result set for release notes or client hand-off.
API Integration
Queue jobs and pull results from CI with scoped keys, per-key rate limits and audit logging.
Workflow
From target to report in four steps
Every job is validated, bounded and recorded. Nothing runs against a host you have not authorized.
1
Configure an authorized target
Add the hostname, publish the verification token, or record an explicit authorization attestation.
2
Choose test parameters
Session count, proxy profile, referrer and timeout — all inside the limits of your plan.
3
Run a controlled test
The worker issues bounded GET requests and classifies each response as pass, blocked or failed.
4
Review and export
Filter by status, target or error category, open the exact diagnostic, then export the set.
Traffic integrity
Built to measure, not to manipulate
The platform is deliberately narrow: authorized targets, bounded sessions on rotating proxies, and a paper trail for every run.
Target authorization
Domain verification tokens or a recorded attestation are required before a job is queued. Private ranges are blocked by default.
Bounded execution
Per-job caps, daily quotas, worker concurrency and hard timeouts keep traffic predictable and attributable.
Audit trail
Sign-ins, job creation, proxy changes and key revocation are recorded with the originating address.
Pricing
Plans that scale with the work
Session allowances and prices are configuration values. Checkout runs through Plisio when the deployment is configured for it.
Starter
For validating a single site before a launch.
$29
/ month · 5,000 sessions
- 5,000 test sessions / month
- Proxy connectivity checks
- Landing page validation
- Standard HTML reports
Professional
For teams running continuous campaign QA.
$99
/ month · 50,000 sessions
- 50,000 test sessions / month
- Advanced analytics
- API access
- Exportable CSV reports
- Domain verification
Business
For agencies and multi-site operations.
$299
/ month · 250,000 sessions
- Custom session limits
- Team access and roles
- Advanced reporting
- Priority support
- Audit log retention
Prices shown are editable defaults (CURRENCY, STARTER_PRICE, PROFESSIONAL_PRICE, BUSINESS_PRICE). Plisio checkout activates when PAYMENT_PROVIDER=plisio and PLISIO_API_KEY are set.
FAQ
Questions worth asking before you start
Which targets can I test?
Any hostname you own or are explicitly authorized to test. Add a domain in the dashboard and verify it with a token file, or record an authorization attestation for a one-off staging check. Targets on this deployment are re-validated on every job.
Do you support authenticated proxies?
Yes. HTTP, HTTPS and SOCKS5 proxies with optional username and password are supported. Credentials stay server-side and are never rendered into the browser.
How are usage limits enforced?
Every job has a per-job cap and the worker enforces bounded concurrency and a configurable request timeout. A daily ceiling can be set by the operator; when it is 0 there is no daily cap. Limits are visible in the dashboard before you start a job.
Is billing live?
Checkout is enabled by the operator. When PAYMENT_PROVIDER=plisio and PLISIO_API_KEY are set, the dashboard creates a Plisio invoice for the selected plan. A plan changes only after Plisio posts a verified completed callback; pending and expired invoices leave the account unchanged.
What is the refund policy?
Refunds apply to the unused portion of a paid period and are reviewed per account. When checkout is disabled, no charge can be made. For a Plisio order, open a support request with the order number and account email.
Does the API require a key?
Yes. Create a key under Dashboard → API. The plaintext is shown once; only a SHA-256 hash is stored. Requests are rate limited per key and every job created through the API lands in the same audit log as the UI.
What data is stored?
Account details, job configuration, HTTP status and latency per session, and an audit trail of account actions. Response bodies are not persisted — only derived metadata such as title and byte count.
What counts as acceptable use?
Load and QA testing of systems you are authorized to test. Sessions render the page in a headless browser with bounded concurrency; no form submissions, no credential use, and no attempt to defeat bot protection. See the Acceptable Use Policy.
Run your first authorized test today
Create an account, verify a hostname, and get a readable verdict on every session.