All systems operational

Provision mailboxes.
Reconcile DNS.
At scale.

Connect multiple Cloudflare and GoDaddy accounts, import every domain into a single inventory, and apply the correct DNS records back to the exact source account — automatically.

12k+
Domains managed
99.9%
DNS write success
< 8s
Avg reconcile time
inbox-terminal
$ inbox reconcile --domain acmecorp.io
→ Resolving provider account [Cloudflare #3]
→ Fetching mailbox DNS requirements…
✓ MX acmecorp.io → smtp.inboxprovider.io [applied]
✓ SPF acmecorp.io → v=spf1 include:… [applied]
✓ DKIM _domainkey → p=MIGfMA0GCSqGSIb3… [applied]
✓ DMARC _dmarc → v=DMARC1; p=quarantine [applied]
✓ Verification passed — 4/4 records live.
Features

Built for serious multi-account domain ops

01

Multi-account providers

Attach multiple Cloudflare and GoDaddy accounts per user. Each domain stays mapped to the account it was imported from — forever.

02

Unified domain inventory

Search, filter, and audit every domain across all provider accounts in a single table. No tab-switching between dashboards.

03

Dynamic DNS source-of-truth

No hardcoded DNS templates. Requirements are fetched live from the mailbox provider at reconciliation time.

04

Verified writeback

Records are applied to the correct provider account, then verified against live DNS before the job is marked complete.

What you get
Provider credentials never exposed to the client
Visible progress + retry flows for every job
Per-record DNS status with live verification
Catch-all enable/disable with loop prevention
Workflow

A clean workflow with visible status

Every action is close to the domains table. Progress steps you can understand at a glance.

1

Connect providers

Add Cloudflare or GoDaddy accounts. Domains sync automatically into one inventory.

2

Provision mailbox

Pick a domain, create a mailbox. Required DNS records are fetched dynamically from the provider.

3

Reconcile DNS

Records are applied to the correct source account and verified live. Job status is visible at every step.

Security

Provider-safe by design

Credentials are stored encrypted server-side. The UI only ever shows connection health, domain mappings, job status, and audit trails — never raw tokens.