Domain Expiry
Look up domain name expiration dates over WHOIS.
Install
pip install lupaxa-domain-expiry
domain-expiry --help
CLI
domain-expiry example.com example.org
domain-expiry --file domains.txt --warn-days 14
python -m lupaxa.domain_expiry --version
Results print as a table with domain, date, and days columns. Every name is
a row, including invalid names and timeouts. The command exits 1 when a
name is due within --warn-days (default 30), already expired, available,
invalid, or has no published date. --sort domain, --sort date, or
--sort days orders the table. --order descending reverses that order.
Library
from lupaxa.domain_expiry import lookup
result = lookup("example.com")
print(result.status, result.expiration, result.days_remaining)
Development
make init
make python-install-dev
make python-check
make mkdocs-serve
Documentation
The published guide is at https://domain-expiry.thelupaxaproject.org/.
Site Markdown lives in mkdocs/.
1 maintainer
Metadata
1 maintainer
Release files for lupaxa-domain-expiry 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lupaxa_domain_expiry-0.1.3.tar.gz | 8.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lupaxa_domain_expiry-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.9 kB
Release files / lupaxa_domain_expiry-0.1.3.tar.gz
| Download URL | lupaxa_domain_expiry-0.1.3.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b834ee24aa445658b64faa48576e8f31babb616d54ab9d8327422dca63ea1985
|
|
BLAKE2b-256 checksum How to use checksums |
996064b129ef847aa503578154e3cc624892c523ed2d5979b658df208f49f9b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logRelease files / lupaxa_domain_expiry-0.1.3-py3-none-any.whl
| Download URL | lupaxa_domain_expiry-0.1.3-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52f4e15f9d34387d62d1d284d013425c75a768475297453027ebb49907fe926b
|
|
BLAKE2b-256 checksum How to use checksums |
104f6c3815240cdf22263e28619fddf917bd11f05e55acafe135ae09c032bab7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency log
