Upload leads · classify via SPF/PTR/HTTP · filter by rules · export with per-company caps · webhook on completion
Reverse-DNS the MX + SPF IPs we already know about. The resulting hostnames go back through the MX matcher and seed the HTTP probe URL list.
Hard caps to prevent a single weird domain (e.g. one with 30 ip4: entries in SPF) from blowing up the fan-out.
Cap on how many distinct IPs we reverse-resolve. Above this, the remainder are dropped (lowest-priority first).
Per-lead concurrency. Worker overall concurrency is capped separately in Rate limits.
Reverse DNS is often slow or absent. This timeout keeps a stuck IP from blocking the others.
Where do we get the IPs to reverse-resolve?
Redis TTL for reverse-DNS results. PTR rarely changes — long TTLs are safe.
Enter a domain and hit Run to see the pipeline trace.