Land in the inbox. Not in spam.
ZKemail warms your domains per ISP, tests where your mail lands, checks your DNS authentication and reads your MTA servers, so a deliverability problem is visible before a campaign pays for it.
Inbox placement
Per-ISP reputation
Warm-up volume
Recent activity
Deliverability is invisible until a campaign fails
ZKemail puts the signals in one place and turns the routine fixes into steps you can review.
Before
Flying blind
- New IPs and domains are pushed too hard before they have a reputation
- You do not know whether mail lands in the inbox, spam or Promotions
- MTA logs, DNS, blocklists and feedback loops live in separate tools
- One wrong DKIM record can quietly hurt a whole sending domain
After
One console
- Volume ramps per ISP, and breakers pause on trouble
- Seed tests report where mail landed, per ISP
- Reputation, bounces, deferrals and DNS findings side by side
- SPF, DKIM and DMARC compared with what is published, with a preview before any change
Email warmup and deliverability, in six parts
Each one covers a piece of deliverability, from the first warm-up send to the inbox. Together they share one view of your senders.
Per-ISP warm-up
Volume ramps on a schedule per mailbox provider, and a circuit breaker pauses sending when bounces or deferrals say reputation is slipping.
Inbox placement
Seed tests send tagged probes and read the seed mailboxes to report inbox, spam, deferred, bounced or missing, per ISP, IP and domain.
DNS authentication
SPF, DKIM, DMARC and BIMI are compared with what is published. Fixes are previewed first, then applied through the Namecheap or NameSilo registrar API.
MTA intelligence
Your MTA servers are read over SSH: reputation, bounces, deferrals and DSN diagnoses, with fleet actions that show what they will change before they run.
AI reputation trainer
A learning pacer suggests volume per ISP. Its output is advisory: deterministic safety limits stay in charge of what actually sends.
Competitive intelligence
A seed inbox collects what other senders mail you, then groups it by brand: subject lines, cadence and where it landed.
From a cold domain to a measured inbox in four steps
Connect your senders
Add your SMTP or MTA servers and your sending domains.
Warm up per ISP
Ramp profiles build volume gradually for each mailbox provider; breakers pause on trouble.
Watch every inbox
Seed tests and the MTA feed show where mail lands and why it was deferred.
Fix and scale
Review DNS and list findings, apply fixes you have previewed, and raise volume when the numbers allow.
Built to hold other people's mail data
What the platform does today. No compliance certificate is claimed on this page.
Access
- Two-factor sign-in (TOTP) available to every account
- Role-based access control (RBAC) with named roles
- Audit logs of privileged actions
Data
- Row-level tenant isolation in the database
- Mailbox and SMTP credentials encrypted at rest (AES-256-GCM)
- Automatic backups
Operations
- Circuit breakers that pause sending on trouble
- Dry-run previews before fleet and DNS changes
- REST API for your own tooling
Privacy policy, terms and a data-processing addendum are in preparation. Ask before you put regulated data into any system.
Questions, answered
What does ZKemail connect to?
Does it send my campaigns?
Can I bring existing domains and IPs?
Is my data separated from other customers?
Does the AI send mail on its own?
How do I get access, and what does it cost?
See where your mail really lands
Start a 7-day free trial to run a seed test, review your DNS authentication and start a warm-up.