Land the send.
Email for product teams. SPF, DKIM, and DMARC on domains you own. Bounces and complaints feed suppression, so one dead address stops getting mail.
Publish five records. Samva signs every send after.
Add your domain and Samva generates the DNS records that prove you own it: ownership, DKIM, and the MAIL FROM pair that moves your mail off a shared subdomain. Once they resolve, Samva signs your outgoing mail and the domain shows verified.
| TYPE | HOST | PURPOSE | STATUS |
|---|---|---|---|
| TXT | _samva | ownership | verified |
| CNAME | s1._domainkey | DKIM | verified |
| MX | send | MAIL FROM | verified |
| TXT | send | SPF | verified |
Prove the mail came from you.
- DKIM signs your outgoing email once the domain verifies, so a receiver can confirm nothing changed in transit
- SPF names the servers allowed to send mail for you
- A DMARC policy ties both together and tells providers what to do with mail that fails
A DMARC policy ties SPF and DKIM together and tells providers what to do when a message fails.
One dead address stops getting mail.
- A hard bounce or a complaint adds the address to a suppression list automatically
- Once suppressed, that address stops receiving mail without you tracking it yourself
- You send from your own domain, so the reputation you build stays yours
The address is added to suppression automatically, so it stops receiving mail without you tracking it yourself.
Inspect delivery on any send.
- Provider-observed opens and clicks appear beside delivery status in the message timeline
- Delivery, bounce, and complaint each arrive as a signed webhook you can act on
- Unique-message rates use eligible delivered mail, while raw observations remain visible
Provider-observed opens and clicks sit beside delivery status. Unique-message rates keep repeated observations from inflating the result.
Every signal that decides where mail lands.
Handled before your first email goes out.
Domain verification
Add a domain and Samva generates the DNS record set you publish to prove ownership.
Bounce and complaint suppression
A hard bounce or a complaint adds the address to suppression automatically.
Unsubscribe groups
Attach a send to an unsubscribeGroupId and Samva keeps every member of that group off it.
Delivery and engagement tracking
Opens and clicks sit next to delivery status in one activity log.
More from the email API.
Common questions.
What do I need before I can send from my own domain?
Add the domain and publish the DNS records Samva generates: an ownership TXT record, three DKIM CNAMEs, and an MX and SPF pair for a custom MAIL FROM subdomain. Once they resolve, the domain shows verified and Samva signs your mail with DKIM.
What does DMARC do that SPF and DKIM don't?
DMARC ties SPF and DKIM together into a policy. It tells providers what to do with mail that fails authentication and reports back on who is sending as your domain, so you see attempts neither record catches on its own.
What happens when an email bounces?
Samva captures the bounce and adds the address to a suppression list automatically. Once an address is suppressed, no further mail goes to it, so one dead address can't keep accumulating bounces against your reputation.
Can I see whether recipients are opening my mail?
Samva records provider-observed opens and clicks in the message timeline and reports unique-message rates against eligible delivered mail. Privacy features, proxies, and security scanners can affect these signals, so use them as directional telemetry rather than proof of a person's intent.
How long does domain verification take?
DNS changes take time to propagate, usually minutes and sometimes a few hours. Samva checks for the published records and flips the domain to verified once they resolve; you don't need to keep the page open.
Verify a domain today.
Sign up, publish the records, and send from your own domain.