• 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

Contact Us

Hosting of RFCI
provided through
the generosity of

whois.rfc-ignorant.org listing policy

Precedent: RFC1032, RFC3912

Type: Domain

RFC1032 specifies that contact data for domains can be found via the WHOIS system.

VERIFICATION OF DATA
The verification process can be accomplished in several ways. One of
these is through the NIC WHOIS server. If he has access to WHOIS,
the DA can type the commmand "whois domain <domain name><return>".
The reply from WHOIS will supply the following: the name and address
of the organization "owning" the domain; the name of the domain; its
administrative, technical, and zone contacts; the host names and
network addresses of sites providing name service for the domain.

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 RFC3912) providing some form of contact information, then by definition no domain in that TLD is RFC1032-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.)