Verification and DNS record state
See required DNS records, verification tokens, and duplicate-record issues before a domain is trusted for MailSlurp send and receive flows.
Branded inbox infrastructure
Use custom domains without giving up API control
Add branded domains, aliases, and environment-specific addresses to MailSlurp workflows so teams can send, receive, test, and route messages from trusted domains.
Trusted by teams shipping customer messaging
Domain controls
Run branded domains as programmable messaging infrastructure
MailSlurp keeps domain setup, inbox creation, aliasing, and catch-all routing in one control plane so branded email stays operationally clean.
Domain-backed inbox and alias provisioning
Create inboxes and aliases on verified domains so support, notifications, QA, and customer-facing workflows use addresses your business actually owns.
Catch-all routing with clear ownership
Attach catch-all behavior to the domain and route unmatched traffic into a controlled inbox instead of relying on ad hoc shared-mailbox forwarding.
Environment separation on one brand
Keep staging, production, and team-specific addresses under the same domain while preserving explicit routing and mailbox ownership.
Custom domains
Key workflows
Custom domains do more than add polish. They separate staging from production, protect reply handling, and keep inbox ownership clear across product, support, and operations workflows.
Workflow 01
Create branded inboxes on demand
Provision inboxes and aliases on your own domain for QA, support, notifications, or customer-facing workflows.
Workflow 02
Split traffic by environment, team, or use case
Keep production, staging, and shared-team inboxes separated while using the same domain and policy model.
Workflow 03
Protect sender trust and reply handling
Pair branded domains with verification, policy checks, and mailbox-level ownership so teams can move faster without creating domain drift.
Developer integration
Use inbox APIs, SMTP, and webhook events in the same workflow
Start with SDK helpers for inbox creation and message waits, then move into event-driven routing when the workflow expands.
- Generated SDKs for major languages
- API + SMTP + IMAP support where needed
- Docs-backed patterns for inboxes and message assertions
Next step
Start with signup or docs
Use the free account to validate the workflow in your own stack, then move into implementation details in the docs.