Add your domain
Enter the domain you own. The app creates an organization-scoped domain profile and an ownership token.
Setup guide
Connect a domain without guessing DNS.
Add a domain, copy exact DNS records, verify destination inboxes, then enable forwarding and outbound sending only after authentication checks pass.
Example DNS records
Production values are generated per domain and provider. These examples show the shape customers should expect.
TXT _mailforward.example.com mf-verify=token MX example.com 10 inbound.mailforward.example TXT example.com v=spf1 include:mailforward.example -all CNAME mf1._domainkey mf1.dkim.provider.example TXT _dmarc v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
Verify DNS records
Copy exact records into your DNS host. The checker verifies ownership, MX, SPF, DKIM, DMARC, and MAIL FROM status.
TXT ownershipMX inboundSPFDKIMDMARCMAIL FROM
Create aliases
Create addresses like support@yourdomain.com, billing@yourdomain.com, and a guarded catch-all when needed.
Verify destination inboxes
Each Gmail, Outlook, Proton, or custom destination confirms a signed verification link before forwarding starts.
Send from the domain
Use generated SMTP/API credentials or a guided Gmail send-as setup after required sender authentication is healthy.
Monitor delivery
Read message metadata logs, bounce events, complaint suppressions, plan usage, and DNS warnings from one dashboard.
Before launch
Configuration checklist.
These are the operational gates that make the service easy to use and safer to run.
Legal
Publish terms, AUP, and privacy docs before signup
Make the rules downloadable and visible before account creation. Include anti-spam, anti-phishing, notice-and-action, complaint, and termination procedures.
DNS
Verify ownership and authentication records
Do not enable production mail until ownership, MX, SPF, DKIM, and DMARC checks are healthy.
Start with managed provider routing
Use SES first for inbound/outbound, retain raw MIME only for processing windows, and store metadata logs by default.
Billing
Enforce paid plans and safe usage limits
Require payment before meaningful outbound volume. Preserve inbound grace periods and pause outbound first when payment fails.
Security
Protect credentials and customer routes
Hash API keys and SMTP passwords, audit sensitive changes, verify provider webhooks, and rate-limit sends.