Upload leads · classify via SPF/PTR/HTTP · filter by rules · export with per-company caps · webhook on completion
Two layers: per-worker (how many leads each worker pod handles in parallel) and per-target-host (how aggressively we hit any one webmail / DNS resolver).
Caps work in flight inside a single worker process. Scale horizontally by adding replicas, not by raising these.
Total leads a worker handles in parallel. Applied at worker start (restart required after change). WORKER_CONCURRENCY env overrides this.
Not yet enforced by the worker — reserved for a future DNS throttle. Prefer per-host HTTP limits below for Stage 1 pace.
Not yet enforced by the worker — reserved for a future global HTTP throttle. Per-host tokens/sec below is what Stage 1 actually uses.
A token bucket per remote host. Without this, the parallel fan-out can hammer a single webmail and get blocked. Takes effect on the next batch the worker claims (no restart). LE_HTTP_HOST_RPS env overrides.
Average rate per host — applied to Stage 1 P3 HTTP probes.
How many tokens accumulate when a host is idle. Allows a brief surge for the fan-out's first wave.
Stricter (or looser) limits for specific hosts. Glob syntax: *.example.com.
| Host (glob) | Tokens / sec | Notes | |
|---|---|---|---|
| No overrides yet. Add one to throttle a specific host. | |||