Deliverability
Mail that arrives, and proof that it did.
The unglamorous half of email. Set up once, checked live, and enforced afterwards.
The records, generated and checked
Add a domain and we generate the exact records to publish — ownership, MX, SPF, DKIM and DMARC — with copy buttons and a check that tells you the moment each one resolves.
- An ownership record, so only you can verify your domain
- One SPF include, merged into the record you already have — never a second SPF record
- A 2048-bit DKIM key for your domain alone — your application never handles one
- A DMARC record at p=quarantine, so mail faking your domain goes to spam
- Domains set up before these records keep working; the new ones are a recommended upgrade
Signed at the server
Outbound mail is DKIM-signed by the mail server itself, so every message leaves signed whether it came from the composer, the API or the SMTP relay.
Bad addresses stop being sent to
A hard bounce or a spam complaint suppresses the address automatically. Reputation is mostly a matter of not repeatedly sending to people who do not want it.
Limits that protect you
Per-plan daily and monthly sending caps are enforced by the API, not displayed on a page. A workspace cannot accidentally burn the shared reputation overnight.
Not in v1
What this page does not claim.
- A domain warm-up dial you configure — per-plan sending caps do the same job without a control that looks broken (D19 removed it)
- Blocklist monitoring dashboards
- A dedicated sending IP