Domains

Production email requires a verified sending domain. Truncus supports per-tenant domain configuration.

Step 1 — Add your domain

Dashboard → Domains → Add domain

Enter your sending domain:

yourapp.com

Truncus will generate the DNS records you need to add.

Add three records to your domain's DNS configuration.

Type: TXT
Name: @
Value: v=spf1 include:truncus.co ~all

If you already have an SPF record, add include:truncus.co to it rather than creating a second TXT record.

DKIM is generated per domain. The name and value are shown in your dashboard.

Type: TXT
Name: truncus._domainkey.yourapp.com
Value: [provided in dashboard]

Type: TXT
Name: _dmarc.yourapp.com
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourapp.com

Start with p=none. Move to p=quarantine or p=reject once you confirm legitimate traffic is aligned.

Verification runs automatically once DNS propagates.

Typical propagation time: 1–5 minutes with Cloudflare. Up to 48 hours with legacy registrars.

Verification status is visible in the dashboard under Domains.

New domains start at a conservative sending limit to protect deliverability reputation.

Warm-up is automatic. Progress is visible in the dashboard.

Mailbox providers monitor sending patterns for new domains. A sudden spike from an unknown domain triggers spam classification.

Gradual ramp-up builds a clean sending reputation before reaching full volume.

Platforms sending email on behalf of their customers can configure per-customer domains.

customerA.com
customerB.com
customerC.com

Each domain maintains independent reputation and suppression lists. A bounce on customerA.com does not affect customerB.com.

See Delivery model → for how suppression lists work.

On the Free plan, you can send from mail.truncus.co without domain configuration. Recommended only for testing.

Production sends should always use a verified domain for deliverability and brand consistency.