User:Jeff G./RFC-Ignorant.Org

RFC-Ignorant.Org was a website and lookup service that billed itself as "the clearinghouse for sites who think that the rules of the internet don't apply to them." It maintained a number of lists ("dsn", "abuse", "postmaster", "bogusmx", and "whois") which contained domains and subnets whose administrators chose not to obey the RFCs, the building block "rules" of the net. It documented who chose not to implement certain protocols described in the RFCs, and provided a means for allowing people to determine for themselves if they wish to communicate with non-compliant systems.

This lists were shut down and the databases were transferred to www.rfc-ignorant.de as of October 30, 2012, but that site was replaced by Sedo Domain Parking by August 29, 2014.

Individual list policies

DSN ( <> )

If the publicly listed MX record for domain refuses to accept mail with a originator given as <>, then the domain will be considered a viable candidate for inclusion in the zone. per RFC 5321 section 6.1 and RFC 2505 sections 2 and 2.6.1.

postmaster

If the right-hand-side of an address doesn't have a postmaster address (e.g., given an address of <foo@example.tld>, if "postmaster@example.tld" bounces as non-existent (on any of the valid MX servers for 'example.tld'), then example.tld would be listed. per RFC 5321 sections 2.3.5, 3.1, 4.1.1.3 BNF grammar, and 4.5.1 paragraph 2 and 3.

abuse

any domain for which abuse@domain is rejected, times-out, or for any other reason cannot be delivered, that shall be considered grounds for listing, excepting as such that if the rejection is obviously based on some criteria which reject the sender. per RFC 2142 section 1 paragraph 1 and section 4.

whois

Domains are listed in the whois.rfc-ignorant.org zone based on meeting any of the following criteria:

1. The information provided in the WHOIS record for a given domain is missing or otherwise "obviously wrong"; examples might include:
   • a phone number of "555-1212";
   • an address of 1060 W. Addison, Chicago (for any organization other than the Chicago Cubs);
   • an address of 1600 Pennsylvania Ave, Washington DC;
   • or an address of No. 10 Downing St., London.
2. If the information provided on a WHOIS record is inaccurate, out of date, or otherwise "provably wrong". This might include e-mails that bounce, phone numbers of people who have nothing to do with the domain, or a street address that doesn't work for the company in question.
3. If the information provided on a WHOIS record acts simply as a redirector, e.g., that someone who calls the number is directed to use one of the other mediums. WHOIS databases contain multiple types of contact info so that people who cannot use one method can use the others. Those alternatives are useless if they simply point people at the others.
4. If a TLD does not have a working, public, free of charge WHOIS registry (operating via TCP port 43, and adhering to the protocol specification in RFC 3912) providing some form of contact information, then by definition no domain in that TLD is RFC 1032-compliant, and that would make the entire TLD a viable candidate for listing, however "entire TLD"-based domains return a different result code in the A record (127.0.0.7 versus 127.0.0.5) so as to allow sites to differentiate between them.
5. If any of the valid MX servers for a domain in the RHS of a contact address have private, reserved, or otherwise bogus IP addresses, then the domain would be listed. (E.g., given an address of <foo@example.tld>, if the MX for example.tld is mail.example.tld, and the A record listed in DNS for mail.example.tld is 127.0.0.1, then example.tld would be listed.)

per RFC 1032 section "VERIFICATION OF DATA" at the bottom of page 5 and RFC 3912 section 2 the WHOIS server replies with text content.

bogusmx

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. per RFC 1035 sections 3.1 Name space definitions (definition labels), 3.3 Standard RRs paragraph 2 (definition domain-name), and 3.3.9 MX RDATA format, RFC 3330 sections 2 Global and Other Specialized Address Blocks and 3 Summary Table, RFC 5321 section 5.1, and RFC 2181 section 10.3 MX and NS recordsElz, Robert and Bush, Randy (July 1997). "RFC 2181 - Clarifications to the DNS Specification". IETF Tools.{{cite web}}: CS1 maint: multiple names: authors list (link)</ref>.

See also

• spamming
• anti-spam techniques (e-mail)
• news.admin.net-abuse.email

External links

• RFC-Ignorant.Org - the homepage of RFC-Ignorant.Org (shut down)