Reputation, isolated. Failure, contained.
Three moves, every mailbox
Add a mailbox. DitLead gives it a dedicated IP. The IP gets watched, swapped, and audit-logged — without you.
Connect a mailbox
OAuth Gmail, Outlook, Microsoft 365 or paste IMAP/SMTP credentials. The moment the mailbox is added, DitLead provisions a dedicated proxy from the matching geo and ISP tier — usually under a second.
Bind a sticky IP
The mailbox is bound 1:1 to its proxy. Every send, IMAP fetch, OAuth refresh and warmup touch routes through the same residential IP, the same way a real person's mailbox does — sticky for the life of the mailbox.
Health watched, IPs swapped
Every proxy is health-pinged every 30 seconds. If latency, blacklist status or reputation score wobbles, we swap to a pre-warmed backup in the same geo + ASN in under a second. The mailbox never notices.
Isolation, geo-match, auto-failover
The three things every other proxy product cuts corners on. We don't.
One mailbox, one IP — never shared
Inbox providers fingerprint by IP, ASN and login geography. A shared IP means dozens of mailboxes look like the same machine — and the moment one spikes spam complaints, the whole cluster's reputation drops with it. Per-mailbox isolation keeps every sender on its own reputation graph.
- Dedicated sticky IP per mailbox — never shared in the same workspace, ever
- Per-mailbox ASN diversity — no /24 collisions across senders
- Independent reputation graph per sender — Gmail can't cluster you
- 1 bad mailbox stays a 1-mailbox problem
Geo-matched, automatically
A US-registered Gmail signing in from a Frankfurt datacenter IP is the fastest possible flag. DitLead matches every proxy to the mailbox's registration country — US to US, EU to EU, JP to JP — and prefers the same state/region when supply allows.
- 190+ countries — residential, ISP and mobile pools
- Auto-match on registration country, state and city when possible
- Per-ASN preference (Comcast for Comcast users, Orange for Orange, etc.)
- Optional locale lock to prevent any cross-geo routing
Health-pinged, auto-failover, zero touch
Every proxy is monitored continuously against the mailbox's own IMAP/SMTP endpoint. If latency spikes, an upstream fails, or the IP lands on an RBL, we swap to a pre-warmed backup in the same geo and ASN — typically inside a second, with no manual intervention.
- 30-second health pings against the mailbox's own endpoint
- Warmed backup pool per geo · same ASN family
- Auto-swap under 1s · zero customer action required
- Blacklist scanning across 80+ RBLs every 5 minutes
Every dial a deliverability lead needs
The settings that turn proxies from a chore into infrastructure you stop thinking about.
Dedicated per mailbox
Every mailbox gets its own IP. No sharing inside a workspace. Ever.
1:1 bindingSticky session
Same IP for the life of the mailbox. Reputation builds where the prospect last saw it.
LifetimeGeo auto-match
Proxy country/state matches the mailbox registration. Mismatch is the fastest flag.
190+ geosISP & residential tiers
Choose residential, ISP, or mobile per pool. Datacenter reserved for warmup only.
3 tiersLive health pings
Every 30s against the mailbox's own SMTP/IMAP endpoint. Real signal, not synthetic.
30-secSub-second failover
Same geo, same ASN family, pre-warmed. Median swap time 0.8s — the mailbox doesn't notice.
<1s swap80+ RBL monitoring
Spamhaus, Barracuda, SORBS and the rest, scanned every 5 minutes per IP.
ContinuousSOCKS5 + HTTPS
Both protocols, both auth styles. Works with every mailbox stack — Gmail, M365, IMAP, OAuth.
UniversalBring your own provider
Already paying Bright Data, Smartproxy, Soax? Paste a credential, DitLead does the routing.
BYOWhat per-mailbox IPs actually move
Illustrative benchmarks, not measured guarantees — your results depend on ICP, offer, list quality and copy.
From founder aliases to 500-mailbox agencies
Same primitive — one mailbox, one IP — different pool size and isolation policy.
Agencies
Each client account stays in its own walled garden. Their mailboxes, their IPs, their geo — no leakage if a client's domain ever has a bad week.
- One client's reputation problem stays one client's problem
- White-label proxy pools per client
- Per-client billing roll-up & audit trail
Sales teams
Each rep's 3–6 mailboxes get their own IP family. If one rep's domain gets flagged, the other reps keep shipping.
- Per-rep pool isolation
- Manager view of every IP's health
- Round-robin to reps without reputation crosstalk
Multi-brand companies
Run brand A, brand B and brand C from one workspace without anyone realizing they share an operator. Different ASNs, different geos, totally separate reputations.
- Brand-scoped IP pools
- Different ASN families per brand
- Per-brand DMARC + return-path control
Founder-led outbound
Five alias mailboxes all routed through five different residential IPs in your city. Looks like five real people, because to every inbox provider it is.
- Same-city IPs for alias mailboxes
- No browser-fingerprint crosstalk
- Persistent across re-auth and warmup
What you get vs what you stop tolerating
Left arrives the day you connect a mailbox. Right is the proxy theater you stop putting up with.
- 01Dedicated sticky residential IP on every mailbox
- 02Geo-matched to mailbox registration country and state
- 03Same ASN family preserved across failovers
- 0430-second health pings on the mailbox's own endpoint
- 05Sub-second auto-failover to a warmed backup IP
- 0680+ real-time blacklist (RBL) scans per IP
- 07SOCKS5 + HTTPS, OAuth + basic auth — universal stack
- 08Included on every paid plan — no per-IP add-on
- 09Bring-your-own proxy provider supported
- 10Full audit log: every send, every IP, every swap
- 01Shared datacenter IPs that cluster your senders
- 02Per-IP add-on bills that punish you for scaling
- 03Rotating proxies that change IP between sends
- 04US mailboxes sending from random EU datacenters
- 05Manual proxy paste-in spreadsheets
- 06One bad mailbox dragging the whole pool down
- 07Discovery of a blacklist after a campaign already failed
- 08Single-IP setups that get flagged in week three
- 09Per-mailbox proxy babysitting across providers
- 10Explaining to your CRO why reply rates collapsed
Proxies that do more than rotate
Most tools call shared pool rotation 'proxies'. DitLead binds one IP to one mailbox and swaps only when reputation wobbles.
| Capability |  DitLead | Instantly | Smartlead | Mailshake | Apollo | Lemlist |
|---|---|---|---|---|---|---|
| Dedicated IP per mailbox (no sharing) | Shared pool | Shared pool | ||||
| Sticky for life of mailbox | Rotating | Rotating | Rotating | Rotating | Rotating | |
| Geo auto-match to registration country | Manual | Manual | ||||
| Residential + ISP tiers (not datacenter) | ISP only | ISP only | ||||
| Health-pinged on mailbox's own endpoint | Synthetic | Synthetic | ||||
| Sub-second auto-failover | Manual | ~minutes | ~minutes | Manual | Manual | |
| RBL monitoring per IP (80+ lists) | Spamhaus | Spamhaus | Spamhaus | |||
| Included on every plan | Add-on | Add-on | Add-on | Add-on | Add-on | |
| Bring-your-own-proxy supported | Limited |
Per-mailbox proxies, explained
Still curious? Our team responds in under an hour.
Talk to sales