Skip to content
nofeb

What is MX record?

Also called mail exchanger record

An MX (mail exchanger) record is a DNS record that names the server accepting email for a domain, with a priority number. Sending servers look up the recipient domain's MX records and try the lowest priority first; without one, mail falls back to the domain's address record or cannot be delivered.

Checked against the engine on .

How does MX record work?

An MX record points at a hostname, never an IP address or a CNAME. Several records with equal priority share the load; a higher number is a fallback. Changing a domain's MX records moves where its mail is delivered, so it is the one email record that can break a working inbox.

MX records also matter for sending: the envelope sender's domain needs an MX that accepts bounces. Sending services that use a custom MAIL FROM subdomain publish an MX on that subdomain only, which leaves the root domain's mail where it is.

Two kinds of MX
example.com.         MX  10  <inbound host>     ; where the domain's mail goes
bounce.example.com.  MX  10  <feedback host>    ; bounces for the MAIL FROM domain only

How does nofeb use MX record?

  • nofeb asks for an MX on the bounce. subdomain for every sending domain; it never touches the root domain's mail.
  • Pointing the root MX at nofeb is a separate, explicit choice: nofeb's own MX then receives the domain's mail with STARTTLS, recipient checks, sender authentication and spam and virus scanning. Publishing through a DNS host's API leaves it out unless you ask.

Frequently asked questions

Will adding nofeb's DNS records change where my mail goes?

Not unless you add the optional root MX. The MX nofeb needs for sending lives on bounce. and only receives bounces.

Where is the MX setting on Namecheap?

Under Advanced DNS → Mail Settings, choose Custom MX first; MX records are added there, not in Host Records.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
Inbound mail server that checks mail at the door nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. Shipped
DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped