|
1 | 1 | # whoisdomain [](https://secure.software/pypi/packages/whoisdomain) |
2 | 2 |
|
3 | | - * A Python package for retrieving WHOIS information of DOMAIN'S ONLY. |
4 | | - * Python 2.x IS NOT supported. |
5 | | - * Python >=3.10 |
6 | | - * Currently no additional python packages need to be installed. |
7 | | - |
| 3 | +- A Python package for retrieving WHOIS information of DOMAIN'S ONLY. |
| 4 | +- Python >=3.10 |
| 5 | +- requirements |
| 6 | + - whodap>=0.1.16 |
| 7 | + - tld>=0.13.2 |
| 8 | +- v1 uses only whois and will be moved to maintenance only |
| 9 | +- v2 will use whodap to first retrieve info with rdap and if no data is available try the classic whois approach |
| 10 | + |
| 11 | + * This package will not support querying ip CIDR ranges or AS information. |
| 12 | + * This was a copy of the original DanyCork 'whois'. |
| 13 | + * Significantly refactored in 2023 (v1). |
| 14 | + * RDAP adding in 2026 (v2). |
| 15 | + * The v1 output is still compatible with DanyCork 'whois'. |
| 16 | + * the v2 will move away from strict compatibility. |
8 | 17 |
|
9 | 18 | --- |
10 | 19 |
|
11 | 20 | ## Notes |
12 | 21 |
|
13 | | -https://en.wikipedia.org/wiki/WHOIS |
| 22 | +### A) https://en.wikipedia.org/wiki/WHOIS |
14 | 23 |
|
15 | 24 | On January 19, 2023, ICANN opened voting on a global amendment to all its registry and registrar agreements. In it they defined an RDAP Ramp-Up Period of 180 days starting with the effectiveness of this amendment. 360 days after this period is defined as the WHOIS Services Sunset Date, after which it is not a requirement for registries and registrars to offer a WHOIS service and instead only an RDAP service is required. All voting thresholds were met within the 60 day voting period and the amendment was approved by the ICANN Board. The date for WHOIS Sunset for gTLDs was set as 28 January 2025.[47] |
16 | 25 |
|
17 | | - * **We are aware of a memory leak** |
| 26 | +### B) **memory leak** |
18 | 27 |
|
19 | | - 2024-02-05: The current whoisdomain has a memory leak, we are currently investigating. |
20 | | - The memory leak is not relevant for short running use but when using whoisdomain in long running programs you should be aware that each query will increase its memory use. |
| 28 | +**2024-02-05: The current whoisdomain has a memory leak.** |
| 29 | + |
| 30 | +The memory leak is not relevant for short running use |
| 31 | +but when using whoisdomain in long running programs |
| 32 | +you should be aware that each query will increase its memory use. |
21 | 33 |
|
22 | | - * This package will not support querying ip CIDR ranges or AS information |
23 | | - * This was a copy of the original DanyCork 'whois'. |
24 | | - * Significantly refactored in 2023. |
25 | | - * The output is still compatible with DanyCork 'whois' |
26 | 34 |
|
27 | | -## Versioning |
| 35 | +### Versioning |
28 | 36 |
|
29 | 37 | * I will start versioning at 1.x.x |
30 | 38 | * the second item will be YYYYMMDD, |
31 | 39 | * the third item will start from 1 and be only used if more than one update will have to be done in one day. |
32 | 40 |
|
33 | 41 | Versions `1.x.x` will keep the output compatible with Danny Cork. |
| 42 | + |
34 | 43 | Versions `2.x.x` will add a dependency on whodap and use rdab based whois data before consulting historical whois. |
35 | 44 |
|
36 | | -## Releases |
| 45 | +### Releases |
37 | 46 |
|
38 | 47 | * Releases are avalable at: [Pypi](https://pypi.org/project/whoisdomain/) |
39 | 48 |
|
40 | 49 | Pypi releases can be installed with: |
41 | 50 |
|
42 | 51 | * `pip install whoisdomain` |
43 | 52 |
|
| 53 | +--- |
| 54 | + |
44 | 55 | ## Features |
45 | 56 | * See: [Features](docs/Features.md) |
46 | 57 |
|
|
0 commit comments