Sending domains changelog

The number of sending domains a workspace can add now depends on its plan:

If a lifetime license is active on the workspace, the license tier’s domain limit applies instead of the plan limit. The limit is checked when you add a domain: the Domains page shows how many domains you use, and Create a domain returns 422 when you’re at the limit. See Domain limits.

• The API and SMTP match the From domain without regard to letter case, so ada@Acme.com sends from the verified domain acme.com.
• Changing a domain’s tracking or inbound subdomain in the dashboard, or with tracking_key and inbound_key in Update a domain, now saves the new value. Publish the DNS record for the new name and verify it.

• API keys created before keys had the secret_ prefix are accepted on /v2 again.
• Retrieve an email returns the full email object, including object, from and to.
• Domain responses return track_loads and track_clicks as 0 or 1, as documented.

On a domain’s DNS Setup tab, Emailit detects Cloudflare nameservers and offers Set up with Cloudflare. Paste a Cloudflare API token with Zone Read and DNS Edit permissions for the zone, choose which optional records to add, and Emailit creates or updates the records and checks DNS again.

The token is stored encrypted so you can sync the records again later, and you can disconnect it at any time. An existing DMARC record isn’t changed. See Set up DNS with Cloudflare.

On Pay as you go, a new domain registered less than 30 days ago waits for approval from the Emailit team before it can send. Once a domain is approved, the approval stays: if its DNS records later fail a check, sending stops until you fix them, but the domain doesn’t need to be reviewed again.

The Domains page title shows a used/limit badge for your plan. See Domain verification.

If a verified domain’s SPF, DKIM or return-path record stops passing, Emailit marks the domain as not verified and emails the workspace owner, so you can fix the record before your sends fail.

Domain verification also compares the DKIM record’s v, k and p values instead of the raw text, so extra spaces, quoting or a different tag order no longer cause a failure. See Domain verification.

To track opens and clicks, publish a CNAME record from go.yourdomain.com (or your custom tracking subdomain) to go.emailitmail.com and verify it. The Track loads and Track clicks switches on a domain turn on only after the record is verified.

Links and open pixels in emails you sent earlier with shared tracking links keep working. See Custom tracking domain.

Add a CNAME record from go.yourdomain.com to go.emailitmail.com to serve tracking links from your own domain, or choose another subdomain with the domain’s tracking key.

Sending Domains are now called Domains in the dashboard, and the API endpoint /v2/sending-domains moved to /v2/domains. See Custom tracking domain.

API keys replace credentials. A key has the full or sending scope, a sending key can be restricted to one sending domain, and you can manage keys through the API. API v1 stayed available while you migrated.

See the API reference.