Managed domain

At signup, every Primitive org is auto-issued a managed sending and receiving subdomain on *.primitive.email. The subdomain is verified by construction (we own the parent zone), so inbound and outbound work the moment your account exists.

What you get

A unique subdomain like brave-otter.primitive.email with MX, DKIM, SPF, DMARC, and TLS-RPT auto-published. Mail to *@<subdomain>.primitive.email (any local part) is delivered through your configured webhooks and API; outbound from the same subdomain is fully authenticated on day one.

When to use it

Dev and test environments, temporary services, and the first few minutes of a Primitive integration before your real domain's DNS finishes propagating.

When to add your own domain

For mail that should look like it's from your business (and pass downstream anti-spoof checks aligned to your domain), bring your own domain. You can run both side by side. Your managed subdomain remains active even after a custom domain is verified. See Domains.

Vanity managed subdomains

Paid plans can rename the auto-generated handle to something brandable (e.g. acme.primitive.email). The replacement is verified by construction the same way; you keep all the same authentication guarantees.

Limits and caveats

• Anyone can verify that *.primitive.email is managed by Primitive. If you need to look independent of the platform, use a custom domain.
• Reputation is shared across Primitive. We police outbound aggressively to protect it; the standard send rate-limits (1k/hr, 10k/day per org) apply.
• The subdomain is permanent for your org once issued. Vanity renames replace the handle but preserve the row.