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.

Yes. HTTP, HTTPS and SOCKS5 proxies with optional username and password are supported. Credentials stay server-side and are never rendered into the browser.

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.

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.

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.

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.

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.

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.