• Domain Based Zones

Mailing List

Submit to:

• DSN ( <> )
• postmaster
• abuse
• whois
• bogusmx

Lookup

Listing Policy:

• General Guidelines
• DSN ( <> )
• postmaster
• abuse
• whois
• bogusmx

Contacting Sites

RSYNC Policy

Hosting of RFCI
provided through
the generosity of

bogusmx.rfc-ignorant.org listing policy

Precedent - Annotated References: RFCs 1035, 3330, 5321, 2181 (not annotated)

Type: Domain

If any publicly listed MX record for domain contains a hostname which points to bogus IP address space, such as those documented in RFC 3330, or IPv6 reservations detailed in RFCs 3879, 4048, 4193, and 4291 or if the domain contains an MX RR that points to an IP address, in violation of RFC 1035 or if the domain has MX RRs which point to hostnames which themselves do not have an associated A record (including MXs which return an NXDOMAIN, or which are CNAMEs)

Also included is any host which resolves to the world broadcast (255.255.255.255) address, since that IP address is obviously invalid.

Just as with an MTA, if there is no MX RR associated with the domain, an implied MX of priority 0 of the hostname itself will be used.

Section 10.3 of RFC 2181 points out that pointing an MX RR at a hostname which is actually a CNAME RR is invalid, and such hosts are also listed.

All MX candidates are considered, and if any of them "fail the test", the domain is listed.

Domains which have bad glue records (e.g., the root servers point to ns5.example.com but the example.com NS set does not list an ns5.example.com) are considered listable, as this sort of situation can lead to undeliverable mail.