Proxy Pool

The proxy pool routes supported network verification through configured proxy endpoints. It is useful when your authorized environment requires controlled egress or when work needs to be distributed across approved network paths.

Add proxies

1. Open Proxy Pool.
2. Add an endpoint manually or import the supported proxy format.
3. Enter authentication only when required.
4. Test the proxy.
5. Enable healthy entries and choose the pool behavior used by a task.

Keep credentials in a trusted local environment. Do not include proxy passwords in screenshots, diagnostics, or exported documentation.

Health and selection

Review connection status, latency, recent failures, and availability before launching a large task. Remove or disable consistently failing endpoints rather than allowing every request to time out.

Test from the same machine and network that will run verification. A proxy can reach general websites while still being unable to perform the DNS or SMTP operation required by a validation mode.

Failure semantics

A proxy failure is an inability to gather evidence. It produces an unknown network result, not an invalid mailbox result. This distinction prevents local network problems from contaminating list quality.

If unknown results rise:

1. Filter them by reason.
2. Compare direct and proxy checks on a small authorized sample.
3. Inspect endpoint health and credentials.
4. Check protocol and port support.
5. Retry only the affected subset after correcting the cause.

Responsible operation

Use endpoints you own or are authorized to use, follow provider terms, and set conservative concurrency. Destination throttling and anti-enumeration behavior are remote policy signals; rotating an endpoint does not convert them into proof that a mailbox exists.

See Settings, updates, and troubleshooting for additional network checks.