Sending
Sending domains & DNS
Authenticate your domain with ownership, DKIM, SPF, return-path and DMARC records, and optionally enable click tracking and inbound mail.
Overview
Mailbox providers decide whether to trust an email largely by checking that the sender’s domain authorised it. When you add a domain, Hulaki generates the DNS records that prove your mail is genuine. You publish them at your DNS provider; we check them automatically and enable sending as soon as the required ones are in place.
Every record is generated for your domain — always copy the exact host and value from Domains → your domain in the dashboard. Examples on this page use acme.com.
Root domain or subdomain?
- Root domain (
acme.com) — recipients see[email protected]. Best for most websites. - Subdomain (
mail.acme.com,news.acme.com) — isolates the reputation of different kinds of mail, and is the right choice if another provider already handles the root domain’s inbound mail.
You can add several domains to a workspace (the number depends on your plan).
The records
| Purpose | Type | Host | Value | Status |
|---|---|---|---|---|
| Ownership | TXT | acme.com | hulakimail-verification=… | Required |
| DKIM | TXT | hulaki._domainkey.acme.com | v=DKIM1; k=rsa; p=<your key from dashboard> | Required |
| SPF | TXT | acme.com | v=spf1 include:_spf.hulakimail.com ~all | Recommended |
| Return-path | MX | send.acme.com | 10 bounces.hulakimail.com | Recommended |
| Return-path SPF | TXT | send.acme.com | v=spf1 include:_spf.hulakimail.com ~all | Recommended |
| DMARC | TXT | _dmarc.acme.com | v=DMARC1; p=none; rua=mailto:[email protected] | Optional |
| Tracking | CNAME | track.acme.com | track.hulakimail.com | Optional |
| Inbound | MX | acme.com | 10 inbound.hulakimail.com | Optional |
send rather than send.acme.com — otherwise you’ll end up with send.acme.com.acme.com.Ownership
A TXT record on the domain itself containing hulakimail-verification= and a unique token. It proves your workspace controls the domain. You can remove it after the domain is verified, but leaving it in place does no harm.
DKIM
DKIM adds a cryptographic signature to every message. When you add a domain, Hulaki generates a 2048-bit key for it, keeps the private half encrypted, and signs every message you send. You publish the public half as one TXT record at hulaki._domainkey.acme.com. The value is longer than 255 characters; most DNS providers split it into several quoted strings automatically, which is fine. DKIM is required — a domain can’t send until the record resolves.
SPF
SPF lists the servers allowed to send for your domain. A domain can only have one SPF record. If you already publish one (for example for Google Workspace or Microsoft 365), don’t add a second — add our include: to the existing record (include:_spf.hulakimail.com) before the final ~all. The dashboard detects your current record and shows the merged value:
; before
acme.com. TXT "v=spf1 include:_spf.google.com ~all"
; after — one record, both senders
acme.com. TXT "v=spf1 include:_spf.google.com include:_spf.hulakimail.com ~all"SPF allows at most 10 DNS lookups; keep your record tidy if you use many services.
Return-path (MAIL FROM)
Bounces are returned to a subdomain you own — send.acme.com by default — instead of a shared address. With the MX and SPF records on that subdomain, your messages pass SPF alignment for DMARC and bounce processing works automatically. You can change the subdomain name when you add the domain.
DMARC
DMARC tells mailbox providers what to do with mail that fails authentication and where to send reports. Gmail and Yahoo require a DMARC record for bulk senders. Start with monitoring and tighten the policy once reports look clean:
_dmarc.acme.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]"
; later: "v=DMARC1; p=quarantine; rua=mailto:[email protected]"
; strictest: "v=DMARC1; p=reject; rua=mailto:[email protected]"If you already publish a DMARC record, keep it — the dashboard will detect it and only flag problems.
Tracking domain
If you enable open and click tracking, links are rewritten through track.acme.com (a CNAME to Hulaki) so they stay on your brand and don’t trip spam filters that distrust shared tracking domains.
Inbound MX
To receive mail in workspace inboxes, enable receiving on the domain and point its MX record at the inbound host shown in the dashboard (priority 10). This replaces any existing mail provider for that domain — use a subdomain if another provider must keep receiving.
Verification & statuses
| Status | Meaning |
|---|---|
| pending | Waiting for the required records. We keep checking for up to 72 hours; click Verify now to check immediately and restart the window. |
| verified | Ownership and DKIM are in place — you can send from any address on the domain. |
| temporary_failure | A previously verified record stopped resolving. Sending continues while we re-check; fix the record to avoid failure. |
| failed | Required records weren’t found within 72 hours, or have been missing for too long. Fix the records and click Verify now. |
Sending from an address on a domain that isn’t verified returns a 403 with code domain_not_verified.
Troubleshooting
- Still pending after an hour? Check for a doubled domain in the host (see the tip above) and for typos or stray quotes in values.
- Look up what the world sees:
dig +short TXT acme.com
dig +short TXT hulaki._domainkey.acme.com
dig +short MX send.acme.com
dig +short TXT _dmarc.acme.com- Two SPF records? Merge them into one; multiple SPF records cause a permanent error.
- CNAME conflicts: a host that has a CNAME can’t have any other record. Remove conflicting records for the tracking host, and make sure
hulaki._domainkeyis a TXT record, not a CNAME.
Step-by-step instructions for popular DNS hosts are in DNS provider guides.
Something unclear or missing? Tell us.