Domains and DNS
Voozin sends only from domains you have verified. Verification publishes the records that prove you own the domain and let receiving servers trust your mail.
Add a domain
In the dashboard open Domains → Add domain. One domain can be used for business mailboxes, API sending, campaigns and inbound routes at the same time. There is no limit on the number of domains.
Records to publish
The domain page lists the exact values for your domain. They typically include:
| Record | Purpose |
|---|---|
TXT @ with v=spf1 … ~all | SPF: authorizes Voozin's servers to send for the domain |
TXT <selector>._domainkey (RSA and Ed25519) | DKIM: signs every message so it cannot be altered |
TXT _dmarc | DMARC: tells receivers what to do with mail that fails SPF and DKIM, and where to send reports |
MX @ | Receives mail for mailboxes and inbound routes |
TXT _mta-sts and CNAME mta-sts | MTA-STS: requires TLS when other servers deliver mail to you |
TXT _smtp._tls | TLS reporting |
If you already send mail from the domain with another provider, merge SPF into a single TXT record (v=spf1 include:… include:… ~all). A domain must have only one SPF record.
The Export button on the domain page downloads the records as a BIND zone file or CSV, which most DNS providers can import.
Verification
Voozin checks the records automatically. Once the required records resolve, the domain becomes Active (status: "ACTIVE") and you can send. Click Verify DNS to check immediately after a change; DNS changes can take up to an hour to propagate, depending on the record's TTL.
Domains over the API
An API key with the domains:read scope can list domains and their DNS status. This is how plugins such as WordPress offer a list of verified sender domains.
curl https://api.voozin.com/v1/domains -H "Authorization: Bearer $VOOZIN_API_KEY"{
"data": [
{
"id": "d3c1…",
"name": "acme.com",
"status": "ACTIVE",
"verified_at": "2026-10-01T09:12:44.000Z",
"track_opens": false,
"track_clicks": false,
"created_at": "2026-10-01T09:02:10.000Z"
}
]
}GET /v1/domains/:id adds dns_records with each record's type, purpose, host, value, priority and status.
Restricting a key to one domain
When you create an API key you can restrict it to one domain. That key can then only send from addresses on that domain, which limits the damage if a key for one site leaks.
Deliverability tips
- Send marketing from a subdomain (for example
news.acme.com) so its reputation is separate from your transactional mail. - Keep DMARC at
p=nonewhile you check reports, then move toquarantineorreject. - A dedicated IP only helps with consistent volume. Most senders do better on the shared, monitored pool.