Address
support@brand.com
Exact alias with catch-all backup and destination verification.
Custom-domain mail, without mail-server work
Create addresses like support@brand.com, forward inbound mail to Gmail or Outlook, and send replies from your own domain with guided DNS setup, delivery logs, pricing, and agent-readable instructions.
Agent-ready summary
Copy a concise brief with what the service does, how setup works, plan pricing, and operational guardrails so an agent can help configure or explain it.

Live domain route
DNS healthyAddress
support@brand.com
Exact alias with catch-all backup and destination verification.
Authentication
SPF + DKIM + DMARC
The setup agent keeps each DNS record visible and rechecks status.
Destination
founder@gmail.com
Forwarded after the destination owner confirms a signed link.
Outbound path
SMTP/API providerMVP surface
The product begins with forwarding and sending, then earns the right to add mailing lists, newsletters, shared inboxes, and webhooks after deliverability and abuse controls are stable.
Organizations own domains, domains own aliases, and every route has verified destinations.
Verified senders, SMTP/API credentials, rate limits, and suppressions are part of the first paid plan.
Customers can see accepted, forwarded, bounced, rejected, deferred, and suppressed events.
Agents
Agents explain what to configure, why it matters, and what to do next when DNS, delivery, billing, or abuse controls need attention.
Setup
Turns confusing DNS tasks into a short checklist with record-level status and plain-language fixes.
Deliverability
Watches authentication, bounce, and complaint signals before they become customer-visible failures.
Billing
Keeps plan limits understandable and avoids surprise inbound mail loss when payments need attention.
Abuse
Guides operators through spam, phishing, malware, complaint, and suspicious signup reviews.
Setup path
The onboarding flow is explicit because email fails quietly when DNS is vague. Every step has exact values, status checks, and a human-readable reason.
Enter the domain you own. The app creates an organization-scoped domain profile and an ownership token.
Copy exact records into your DNS host. The checker verifies ownership, MX, SPF, DKIM, DMARC, and MAIL FROM status.
Create addresses like support@yourdomain.com, billing@yourdomain.com, and a guarded catch-all when needed.
Each Gmail, Outlook, Proton, or custom destination confirms a signed verification link before forwarding starts.
Use generated SMTP/API credentials or a guided Gmail send-as setup after required sender authentication is healthy.
Read message metadata logs, bounce events, complaint suppressions, plan usage, and DNS warnings from one dashboard.
Product console
Customers should not need to know mail-server internals. They need to see what is connected, what is healthy, what is blocked, and what changed.
DNS verification
| Type | Host | Value | Status |
|---|---|---|---|
| TXT | _mf.brand.com | ownership token | valid |
| MX | brand.com | inbound.mailforward.example | valid |
| DKIM | mf1._domainkey | provider key | valid |
| DMARC | _dmarc | p=quarantine | warning |
| Time | Direction | Address | Status |
|---|---|---|---|
| 09:20 | Inbound | support@brand.com | forwarded |
| 09:18 | Outbound | hello@brand.com | delivered |
| 09:03 | Inbound | billing@brand.com | forwarded |
| 08:41 | Outbound | news@brand.com | suppressed |
Pricing
Inbound mail gets grace periods. Outbound sending stays controlled because shared reputation is part of the product.
$5/mo
One domain, professional aliases, and safe forwarding.
$12/mo
For founders running several addresses and domains.
$29/mo
Team-ready routing, logs, and higher safe volume.
$79/mo
Many domains for client work with review-friendly controls.
Launch readiness
The public service needs clear legal documents, DNS checks, mail-provider settings, billing controls, and credential safety before production traffic.
Legal
Make the rules downloadable and visible before account creation. Include anti-spam, anti-phishing, notice-and-action, complaint, and termination procedures.
DNS
Do not enable production mail until ownership, MX, SPF, DKIM, and DMARC checks are healthy.
Use SES first for inbound/outbound, retain raw MIME only for processing windows, and store metadata logs by default.
Billing
Require payment before meaningful outbound volume. Preserve inbound grace periods and pause outbound first when payment fails.
Security
Hash API keys and SMTP passwords, audit sensitive changes, verify provider webhooks, and rate-limit sends.