Envello
Authentication and DNS

MX record

An MX record tells other mail servers which hosts accept mail for a domain, with a priority number. Lower numbers are tried first.

MX records only govern receiving. Sending through an API doesn't need them, and changing them doesn't affect outbound mail. A domain with no MX record can still receive mail at its A record in theory, but in practice you should publish an explicit null MX (a single MX of priority 0 pointing at .) if a domain never receives mail, per RFC 7505.

Address validation looks up MX records to tell whether a domain can receive mail at all, which is a cheap way to catch typo domains at signup.

In Envello

POST /emails/validate checks an address's syntax, its domain's MX records and known disposable domains.

Read next

Related terms

All glossary terms