Domains
Verify a domain to send from it. Verification proves ownership and sets up DKIM signing, SPF, and a branded envelope sender — everything inbox providers check.
Add a domain
Dashboard → Domains → Add domain. Enter the bare domain (acme.com) — you can then send from any address on it (hello@acme.com, receipts@acme.com, …). Adding a subdomain like mail.acme.com works the same way.
Publish the DNS records
Sendibl shows the records to publish. There are three kinds:
| Field | Type | Description |
|---|---|---|
| _sendibl TXT | TXT | An ownership token proving you control the domain. |
| DKIM CNAMEs | CNAME ×3 | Point to our signing keys so your mail is cryptographically signed as your domain. |
| send SPF + MX | TXT + MX | On send.yourdomain.com: authorizes sending and routes bounce feedback. This subdomain becomes your branded envelope sender (what Gmail shows as mailed-by). |
_sendibl, not _sendibl.acme.com — or you'll create _sendibl.acme.com.acme.com; (2) remove any older MX record on send.yourdomain.com left by a previous provider — conflicting MX records prevent the branded envelope sender from activating.One-click Cloudflare setup
If your DNS is on Cloudflare, choose Auto-configure and paste a Cloudflare API token scoped to Zone:Read + DNS:Edit. Sendibl creates every record in your zone in one shot. The token is used for that single request and never stored — you can delete it in Cloudflare immediately after.
Verify
Click Verify once records are published. Verification checks the ownership TXT and confirms DKIM is active; DNS propagation plus DKIM detection typically takes a few minutes (up to ~15). The domain flips to verified and you can send. In production, sends from unverified domains are rejected with 403.
Open & click tracking
Each domain has two toggles, applied to mail sent from it:
| Field | Type | Description |
|---|---|---|
| open_tracking | boolean | Embeds a tracking pixel; the first open records an opened event and increments the open count. |
| click_tracking | boolean | Rewrites links through Sendibl; each click records a clicked event with the destination URL, then redirects. |
Deleting a domain
Deleting a domain stops it from being usable for sending. Your DNS records are yours to remove — Sendibl never touches your zone outside the explicit auto-configure action.
POST /domains {"name": "acme.com"}
GET /domains
POST /domains/:id/verify
POST /domains/:id/autoconfigure {"cloudflare_api_token": "..."}
PATCH /domains/:id {"open_tracking": true, "click_tracking": false}
DELETE /domains/:id