LLPROBeta

Home / Businesses / MX Record Check (RFC 5321 / RFC 7505)

MX Record Check (RFC 5321 / RFC 7505)

Check a domain's MX answers: delivery order, null MX (RFC 7505), duplicates, IP-address or invalid exchanges and hosts with no address, each problem with its RFC, signed.

Testing

What it does
Check a domain's MX answers: delivery order, null MX (RFC 7505), duplicates, IP-address or invalid exchanges and hosts with no address, each problem with its RFC, signed.
Who it is for
Businesses.
Start in one step
Ask your agent to call mx_record_check at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

MX Record Check (RFC 5321 / RFC 7505) is for agents that set up or fix a business's email (new domain, migration, bounces, mail that never arrives) and need the MX records checked before and after they go into DNS. Check the MX answers for a domain, before you publish them or when mail to the domain bounces or never arrives. Send the MX records you got (preference and exchange host) and, optionally, the hosts that have an A or AAAA address answer, and the domain. Get back the order senders will try the hosts in (lowest preference first, equal preferences shared), whether it is a valid null MX (RFC 7505: the domain accepts no mail), and each problem with its RFC: duplicate records, the same host at two preferences, a null MX mixed with other records, an exchange that is an IP address or not a valid host name, and hosts with no address. No DNS query is made: you send the answers. It is one of the Email department tools LLPRO builds for the work agents do across business software (Gmail, Outlook, Google Workspace, Microsoft 365, Sendgrid). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that set up or fix a business's email (new domain, migration, bounces, mail that never arrives) and need the MX records checked before and after they go into DNS.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, records up to 200 entries, address_hosts up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Makes no DNS query: it does not fetch the MX records, check that a host's address is reachable or accepts mail on port 25, follow a CNAME (an MX target must not be an alias, RFC 2181 section 10.3: that needs a DNS lookup), or check SPF, DKIM or DMARC. Whether a host with no address is really missing one depends on the address list you send. Not legal or technical advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "mx_record_check", "arguments": {"records": [{"preference": 20, "exchange": "mx2.example.com."}, {"preference": 10, "exchange": "MX1.Example.com"}], "address_hosts": ["mx1.example.com", "mx2.example.com"], "domain": "example.com"}}}

For agents

Tool mx_record_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:vzzzmubfroo75z2lwom5owls24): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): oWCtnG3JUYAdbHpk0HSkzDGIufrF1VfMdqA64VsOaf4=

For agents that search MCP registries for MX record, null MX, mail exchanger tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card