Haku

Perfect leads get wasted without mailboxes built for outbound

Domain health, authentication, warm-up and sending limits are managed alongside the cadence rather than bolted on afterwards. Volume is capped by what the inbox will accept.

Domain health · 4 domainsall authenticated
Check
State
Detail
SPF
pass
aligned
DKIM
pass
2048-bit
DMARC
pass
p=quarantine
Warm-up
active
day 14 of 21
Inbox placement
monitored
seed tested
Bounce rate
0.4%
under cap
Spam complaints
0.01%
under cap
Checked hourly · illustrative data
✓
Achieve 95% deliverability
Inbox placement monitored with seed testing, not guessed at from open rates.
⚙
Automatic domain and mailbox setup
Domains bought, records written and mailboxes provisioned without a ticket to IT.
◉
Continuous warmup
Warmup never switches off. Volume ramps and holds against real engagement.
◆
Dedicated IP, never shared
Your reputation is yours alone. No pooled sending with strangers' campaigns.
✓
Achieve 95% deliverability
Inbox placement monitored with seed testing, not guessed at from open rates.
⚙
Automatic domain and mailbox setup
Domains bought, records written and mailboxes provisioned without a ticket to IT.
◉
Continuous warmup
Warmup never switches off. Volume ramps and holds against real engagement.
◆
Dedicated IP, never shared
Your reputation is yours alone. No pooled sending with strangers' campaigns.

How sending is protected

01

Authenticate first

SPF, DKIM and DMARC are verified before a single message is queued, per sending domain.

02

Warm up in sequence

New mailboxes ramp over three weeks against real engagement, not synthetic volume.

03

Cap and pause

Sending is capped per mailbox and paused automatically when bounce or complaint rates drift.

Limits and controls

Caps are set per mailbox and per domain, and the cadence respects them. If a domain degrades, sending pauses before reputation is lost.

per mailbox
Daily send caps set per mailbox, with the cadence queueing rather than overrunning them.
suppression
Global suppression across the workspace, so two reps never hit the same contact.
verification
Addresses re-verified before send, not only at enrichment time.
consent
Unsubscribe and objection handling recorded against the contact and honoured across all channels.
Next in the loop 06Reporting 01ICP Intelligence 02Account Identification 03Waterfall Enrichment 04Multichannel Engagement
Cameron Evans
"Everyone is saying different things, Microsoft, Google, SMTP, DMARC - email outreach is a new world. Here's what we are seeing works"
Cameron Evans
Founder, Haku
Read the Deliverability Guide 2026
Deliverability — Haku

Perfect leads get wasted without mailboxes built for outbound

Domain health, authentication, warm-up and sending limits are managed alongside the cadence rather than bolted on afterwards. Volume is capped by what the inbox will accept.

Book a demo
Domain health · 4 domainsall authenticated
Check
State
Detail
{{ w.attr }}
{{ w.weight }}
{{ w.delta }}
Checked hourly · illustrative data
{{ r.icon }}
{{ r.title }}
{{ r.body }}

How sending is protected

{{ s.num }}

{{ s.title }}

{{ s.body }}

Limits and controls

Caps are set per mailbox and per domain, and the cadence respects them. If a domain degrades, sending pauses before reputation is lost.

{{ l.tag }}
{{ l.text }}
Next in the loop 06Reporting 01ICP Intelligence 02Account Identification 03Waterfall Enrichment 04Multichannel Engagement
Cameron Evans
"Everyone is saying different things, Microsoft, Google, SMTP, DMARC - email outreach is a new world. Here's what we are seeing works"
Cameron Evans
Founder, Haku
Read the Deliverability Guide 2026