richardpenman / whois

MIT License
346 stars 179 forks source link

.pro domain lookups don't work #198

Open twbryan opened 6 months ago

twbryan commented 6 months ago


In [2]: whois.whois("tech.pro")
Error trying to connect to socket: closing socket - [Errno 8] nodename nor servname provided, or not known
Out[2]:
{'domain_name': None,
 'registrar': None,
 'whois_server': None,
 'referral_url': None,
 'updated_date': None,
 'creation_date': None,
 'expiration_date': None,
 'name_servers': None,
 'status': None,
 'emails': None,
 'dnssec': None,
 'name': None,
 'org': None,
 'address': None,
 'city': None,
 'state': None,
 'registrant_postal_code': None,
 'country': None}```
case-fastly commented 6 months ago

According to https://www.iana.org/domains/root/db/pro.html, the whois server URL is now whois.nic.pro -- maybe that's the issue?

skibine commented 4 months ago

According to https://www.iana.org/domains/root/db/pro.html, the whois server URL is now whois.nic.pro -- maybe that's the issue?

Nope. It is not the issue. And .pro domains - are not the only. Try .sc, for example maven.sc or nic.sc. But by the way, from console i can whois .pro domains (from python - nope), and .sc domains do not work either under the console or under Python. And whois maven.sc --verbose shows "Using server whois2.afilias-grs.net" - it is correct, according to iana, and from web-interface "whois2.afilias-grs.net" - all works well. I don't know where to dig. It seems to me that there are several reasons and they came together at the same time.

case-fastly commented 4 months ago

Fwiw, these zones (.pro, .sc, etc) moved from the Afilias registry backend operator to Identity Digital on 2023-08-01. You might consider contacting the Technical Contact email address here -- https://www.iana.org/domains/root/db/pro.html -- and asking why whois.nic.pro doesn't seem to be working.

https://www.prnewswire.com/news-releases/donuts-inc-and-afilias-inc-rebrand-to-identity-digital-301572401.html

https://en.wikipedia.org/wiki/Afilias

mzpqnxow commented 3 weeks ago

Fwiw, these zones (.pro, .sc, etc) moved from the Afilias registry backend operator to Identity Digital on 2023-08-01. You might consider contacting the Technical Contact email address here -- https://www.iana.org/domains/root/db/pro.html -- and asking why whois.nic.pro doesn't seem to be working.

https://www.prnewswire.com/news-releases/donuts-inc-and-afilias-inc-rebrand-to-identity-digital-301572401.html

https://en.wikipedia.org/wiki/Afilias

I believe that .pro is considered a Generic TLD (gTLD) but I could be wrong

If it is, the WHOIS server should be available at whois.nic.pro (which does resolve, though I haven't checked an actual WHOIS request)

BillWeissABK commented 2 weeks ago

For what it's worth, this is working without any change for me. I think @mzpqnxow 's comment is correct, this doesn't need special whois servers anymore.

➜ python3
Python 3.12.3 (main, Apr  9 2024, 08:09:14) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import whois
>>> whois.whois("tech.pro")
{'domain_name': 'tech.pro', 'registrar': 'Dynadot7 LLC', 'registrar_url': ['https://dynadot.com', 'http://www.dynadot7.com'], 'whois_server': 'whois.dynadot7.com', 'referral_url': None, 'updated_date': [datetime.datetime(2024, 6, 17, 10, 17, 11), datetime.datetime(2024, 5, 6, 6, 30, 27)], 'creation_date': datetime.datetime(2020, 5, 3, 10, 16, 53), 'expiration_date': datetime.datetime(2025, 5, 3, 10, 16, 53), 'name_servers': ['leah.ns.cloudflare.com', 'sevki.ns.cloudflare.com'], 'status': 'clientTransferProhibited https://icann.org/epp#clientTransferProhibited', 'emails': 'abuse@dynadot7.com', 'dnssec': 'unsigned', 'name': 'REDACTED FOR PRIVACY', 'org': 'Super Privacy Service LTD c/o Dynadot', 'address': ['REDACTED FOR PRIVACY', 'PO Box 701'], 'city': ['REDACTED FOR PRIVACY', 'San Mateo'], 'state': 'California', 'registrant_postal_code': ['REDACTED FOR PRIVACY', '94401'], 'country': 'US'}
lelutin commented 2 weeks ago

I can confirm what @BillWeissABK said. with python 3.11.9 the same excerpt gives me a bunch of information without errors.

@twbryan can you try again on the latest commit on the master branch to see if the issue is fixed for you too?