Why use hosted MTA-STS?
MTA-STS (RFC 8461) requires hosting a policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. This means you need:
- A subdomain with a valid HTTPS certificate
- A web server to serve the policy file
- Ongoing maintenance to keep certificates renewed
With hosted MTA-STS, you skip all of that. Just add DNS records and we handle the HTTPS hosting, certificate management, and policy serving.
How it works
1. Create your policy
Sign in and create a new policy. Choose your domain, mode (testing/enforce), MX patterns, and cache duration.
2. Verify domain ownership
Add the TXT verification record we provide to your DNS. This proves you control the domain.
3. Add deployment DNS records
Add two DNS records:
- CNAME: Points
mta-sts.yourdomain.comto our policy server - TXT: Advertises your MTA-STS policy at
_mta-sts.yourdomain.com
That's it. Your MTA-STS policy is live and serving.
When to use hosted vs. self-hosted MTA-STS
| Feature | Hosted (CaptainDNS) | Self-hosted |
|---|---|---|
| Web server setup | Not needed | Required |
| HTTPS certificate | Automatic | Manual (Let's Encrypt, etc.) |
| Policy updates | Dashboard + auto rotation | Manual file editing |
| Multiple domains | Single dashboard | Per-domain server config |
| Downtime risk | Redundant infrastructure | Depends on your setup |
| Cost | Free | Server hosting costs |
Choose hosted if you want zero infrastructure overhead. Choose self-hosted if you need full control over the policy endpoint.
Complementary tools
| Tool | Description |
|---|---|
| MTA-STS Generator | Generate MTA-STS records and policy files |
| MTA-STS Record Checker | Validate your MTA-STS configuration |
| MTA-STS Syntax Checker | Validate MTA-STS syntax offline |
| TLS-RPT Generator | Set up TLS reporting alongside MTA-STS |