.com parsing fails for IANA domains
See original GitHub issueDescribe the bug
Domains registered under .com by IANA directly output a different format, thus causes the parsing to fail. An example is example.com
. Instead for regular format, it has the following output:
domain: EXAMPLE.COM
organisation: Internet Assigned Numbers Authority
created: 1992-01-01
source: IANA
To Reproduce Steps to reproduce the behavior:
- Query to example.com
- Try to access
.__dict__
Expected behavior Should deal with the IANA format
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
IDN Repository Procedures
The sole purpose of the repository is to publish LGRs that have been verified as coming from representatives of domain registries. Registries ...
Read more >How can I find the WHOIS server for any TLD? [closed]
The 100% reliable method is to look up the TLD at IANA's WHOIS server, whois.iana.org , parse out the whois: entry, and then...
Read more >How do I get the domain originating the request in express.js?
You have to retrieve it from the HOST header. var host = req.get('host');. It is optional with HTTP 1.0, but required by 1.1....
Read more >DomainValidator (Apache Commons Validator 1.7 API)
No accommodation is provided for the specialized needs of other applications; if the domain name has been URL-encoded, for example, validation will fail...
Read more >Parsing DNS query and response fields - IBM
DNS response ; Query domain, The domain name that was requested to be resolved. ; Response code, A response code of 0 means...
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
fixed now in https://github.com/DannyCork/python-whois/pull/233
should be fixed by pull request: #230