Land in the inbox, with reputation handled.
You send on domains you own with SPF, DKIM, and DMARC set up for you. Each bounce and complaint feeds suppression on its own, so one dead address stops getting mail before it touches the reputation behind the rest of your sends.
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 |
| TXT | _dmarc | DMARC | verified |
SPF, DKIM, and DMARC, on domains you own.
- DKIM signs every outgoing message once your domain verifies, so a receiver can confirm it wasn't altered in transit
- SPF declares which servers are allowed to send mail on your behalf
- 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.
Bounces and complaints feed suppression on their own.
- 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
- Each organization's sending reputation is isolated, so it isn't dragged down by anyone else's
The address is added to suppression automatically, so it stops receiving mail without you tracking it yourself.
Delivery signals you can verify per send.
- Opens and clicks are recorded and surfaced alongside delivery status in your dashboard
- Delivery, bounce, and complaint each arrive as a signed webhook you can act on
- Engagement is a trend to read, not a guarantee, so you see what is landing and what isn't
Opens and clicks sit next to delivery status in your dashboard activity log, so you see which sends are landing.
Every signal that decides where mail lands.
Handled before you send your first message.
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.
The rest of the email channel.
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?
Yes. Samva records opens and clicks and surfaces them next to delivery status in your dashboard activity log, so you can see which sends are landing and which are going unread.
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 and publish the records that put your mail in the inbox.