![](https://secure.gravatar.com/avatar/2007180f6bb0e8aea5b9cf7d3788bea6.jpg?s=120&d=mm&r=g)
Does anyone have a contact for OneAndOne. Their abuse email address appears to be a black hole and they are becoming a haven for phishing websites. ---
![](https://secure.gravatar.com/avatar/a0bc4d3b9487ff94ae175fa156dc314e.jpg?s=120&d=mm&r=g)
Over the past few days I have come to realize the not all of the TLD WhoIs servers seems to use or support a common query format and I was hoping someone on this list might be able to point me to forum or web page where I can find more information on this subject. For instance I have found the whois.arin.net will respond with a helpful reply if it does not accept the arguments or prefixes for an IP query. It responds to let me know that I can get more information about the query format by sending it a query with noting but '?\r\n' but whois.ripe.net is not nearly as helpful and simply complains, without offering any information about how or where one might find details about acceptable arguments. TIA
![](https://secure.gravatar.com/avatar/4b064bf60d208e1df2586e95a1ab81d2.jpg?s=120&d=mm&r=g)
In article <3f032924-7298-9034-a22f-6264ed6c3aa6@telus.net> you write:
Over the past few days I have come to realize the not all of the TLD WhoIs servers seems to use or support a common query format and I was hoping someone on this list might be able to point me to forum or web page where I can find more information on this subject.
No kidding. Most of the ICANN contracted gTLDs use the same format, defined in Specification 4 of the standard registry agreement. https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved... Except that .COM and .NET are "thin" registries that only have a small part of the data, with the rest at each registrar. The registrar whois is utterly random. Most country ccTLDs don't have any useful whois, and again the ones that do have wildly different formats. I have a 3500 line perl module that tries to scrape whois with limited success, particularly since most registrars now redact nearly everything with GDPR as the excuse. There's a new RFC defined scheme called RDAP that uses http queries and JSON responses that is nearly trivial to parse. All the ICANN contracted registries and registrars are supposed to switch to RDAP at some point but I'm not holding my breath.
For instance I have found the whois.arin.net ...
The RIRs are different. They actually do have RDAP servers that work pretty well. Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
![](https://secure.gravatar.com/avatar/a0bc4d3b9487ff94ae175fa156dc314e.jpg?s=120&d=mm&r=g)
@John & @Martin Obviously I will need to do a fair bit more research on this topic. ;-) Thank you both for your helpful advise and comments; they give me a very good starting point. Arnold
participants (3)
-
garbage@storey.ovh
-
John Levine
-
wiegert