返回资讯中心
外部精选
软件工程
#开发者实时流

I checked 8,062 Show HN domains: 223 send with Resend and have no MX record

An MX (mail exchanger) record tells other mail servers which host accepts mail for a hostname. Each one pairs a priority number with a hostname, and senders try the lowest number first. MX is looked up per hostname, so …

Hacker News 最新raress962026/10/20 · 26 天前10 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

An MX (mail exchanger) record tells other mail servers which host accepts mail for a hostname. Each one pairs a priority number with a hostname, and senders try the lowest number first. MX is looked up per hostname, so updates.yourdomain.com can have its own MX records and receive mail somewhere else while yourdomain.com keeps Google Workspace. Our guide to email on a subdomain sets that up on a live domain.

A hostname with no MX at all doesn't simply refuse mail: senders fall back to its A record, as RFC 5321 section 5.1 describes, and that usually points at a web server, not a mail server.

Next to the pill you get the provider when the hostname makes it clear, or else the host itself, plus a one-line verdict. Open a domain to see its MX table: each host in priority order, the cached TTL, and whether the host resolves over IPv4 and IPv6.

Lower priority numbers are tried first, and hosts with equal numbers share the load. A single host is normal, so we don't flag a missing backup. The TTL is how long resolvers may cache the records, which is how long a change can take to reach everyone. The TTL (cached) column shows the time left in the public resolver's cache, so it can be lower than the value you set. Each MX lookup reads live public DNS, so you see what senders see right now.

If the provider label looks wrong, compare your records with what your provider asks for:

Google's MX setup page lists the single smtp.google.com host. Setups from before 2023 may still use the legacy aspmx.l.google.com set, which still works. Personal Gmail addresses run on Google's own gmail-smtp-in.l.google.com hosts, which the checker labels Gmail. For Microsoft 365, External DNS records for Microsoft 365 explains where to find your MX token in the admin center. Zoho's values above are for the US data center, and other data centers use other hosts, so copy the ones your Zoho admin console shows. Cloudflare Email Routing assigns its own priorities, so copy what the dashboard shows.

Replies to mail you send from a domain like that bounce, so the customer who answers your receipt never reaches you. Our guide to replying from a custom domain covers getting those replies back.

Also check what the new MX gives you. A forwarding MX like Cloudflare Email Routing only receives: it passes mail on to a mailbox you already have, so you still need something else to reply from your domain.

MX covers receiving. For sending, run the same domains through the DMARC checker, which reads DMARC and SPF. And if you're choosing email hosting for several domains, that guide compares the options.

Paste it in the box at the top of this page and click Check MX records. From a terminal, run dig MX yourdomain.com on macOS or Linux, or nslookup -type=mx yourdomain.com on Windows.

The DNS record that names the mail server accepting mail for a hostname, with a priority number. Senders look it up before they deliver anything to an address at that hostname.

Lower is tried first. Hosts with equal priorities share the load, and higher numbers are backups that senders try when the lower ones don't answer.

Yes, MX is per hostname, so updates.yourdomain.com can receive mail somewhere other than yourdomain.com. The only blocker is an existing CNAME on the same name, which has to go first.

Senders try the domain's A or AAAA address instead (RFC 5321), which usually isn't a mail server, so mail and replies to it bounce.

An MX record of 0 ., from RFC 7505. It says the domain accepts no mail, so senders give up right away instead of retrying. It's correct for parked domains, and it must be the only MX record on the name.

Up to the old record's TTL, which the results show (as the resolver reports it, so it can be lower than the value you set). This tool reads live public DNS, so it shows what resolvers see now.

Yes, up to 10 domains or subdomains per run, with no account.

No. Lookups run live over public DNS (Cloudflare's resolver, with Google's as a fallback), and nothing is saved or logged. Our analytics only counts how many domains you checked, never which ones, and a shared results link keeps the domains after the #, which browsers don't send to our server.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →