Return None when whois Internationalized domain name
See original GitHub issueThank you for your awesome package *)
Describe the bug
domain = whois.query('münchen.de')
print(domain.__dict__)
domain = whois.query('ایران.ir')
print(domain.__dict__)
error:
AttributeError Traceback (most recent call last)
Input In [9], in <cell line: 1>()
----> 1 domain.__dict__
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Internationalized domain name - Wikipedia
An internationalized domain name (IDN) is an Internet domain name that contains at least one label displayed in software applications, in whole or...
Read more >pythonwhois returns none value for contact information for ...
I used get_whois(domain) function of pythonwhois 2.4. 3 for retrieving whois information for domains. But when I enter domains with specific ...
Read more >Internationalized Domain Names (IDN) FAQ - Unicode
Q: Do IDNs change the Domain Name System (DNS)?. No. Internally, the non-ASCII Unicode characters are transformed into a special sequence of ASCII ......
Read more >RFC 3490: Internationalizing Domain Names in Applications ...
This document defines internationalized domain names (IDNs) and a mechanism called Internationalizing Domain Names in Applications (IDNA) for handling them ...
Read more >What are Internationalized Domain Names (IDNs)? - GoDaddy
Internationalized Domain Names (IDNs) are foreign language domain names that include non-ASCII characters. You can register an IDN using the native language ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yes i see that this is creating a error in the latest release but the latest code already solves this
I guess we have to wait for the latest code to be released into a pip package, meanwhile you could clone the code and us it directly
0.9.18 released