Verify a domain

To send mail from a domain (for example, notifications@yourcompany.com) you must prove you own that domain. Verification is done from the dashboard, by publishing a TXT record in your DNS — a standard process that doesn’t affect your email or any other services on the domain.

Note

Domain setup (adding, verifying, authorizing keys) lives at the account level and is managed in the dashboard, not via an API key. The API key is used to send; the domain is verified once in the panel.

Verification flow

1. In the dashboard go to Domains → Add domain and enter your domain (for example yourcompany.com).
2. The panel shows you a unique verification TXT record. Publish it at your DNS provider (Cloudflare, Route 53, Namecheap, etc.).
3. Click Verify. The system does a DNS lookup of the TXT record and, if it finds it, marks the domain as verified.

The verification record

The panel gives you a record shaped like this (the exact token is shown in the panel):

Field	Value
Name / Host	_md-verify.yourcompany.com
Type	TXT
Value	md-verify=abc123xyz
TTL	Any (3600 seconds is fine)

The TXT record can stay permanently

The verification TXT doesn’t interfere with mail flow, SPF, or any other record in your DNS. You can leave it published indefinitely — there’s no need to remove it after verifying.

DNS propagation can take time

If you click Verify and it isn’t detected yet, wait 5–10 minutes and try again — DNS propagation is sometimes slow. You can confirm the record is visible with dig TXT _md-verify.yourcompany.com. The Re-check DNS button on the Domains page forces a live re-check (handy right after publishing the record).

Without a verified domain you can’t send

Trying to send mail (transactional or campaign) with a from_email whose domain isn’t verified returns 403 Forbidden with code domain_unauthorized. The error is returned at request time, before the message is queued.

Authorizing your API keys

Verifying the domain proves ownership; which API keys can send from it is decided by your account’s domain↔key access model. See the Key access to domains guide for the details.

Next step

With the domain verified, set up your email authentication records: SPF, DKIM, and DMARC. These records improve deliverability and protect your domain from spoofing. See the SPF, DKIM & DMARC guide.