DNS Utils
Why this library ?
I worked on DNS/Registrar analysis and consolidation over a few months, and something we quickly notice is that:
- Not everything is standardized (E.g. Whois database response)
- The RFC are very verbose and most developers don't want to go through all of it for their simple needs.
- The way the DNS respond is not ideal for development. For example, it is better to receive an empty list when no records are found that throwing an error "No record".
- Having typing on these information helps a lot and ensure correctness.
This library is, for a big part, a layer on top of dnspython
Current status.
This library was developed progressively over months as per needed. It was not designed upfront as many things got discovered along the road.
- The current API is supposed to be stable, the underlying behaviour might be changed for correctness if needed, but retrocompatibility should be kept.
- The current API will hopefully be completed with additional features.
Contributing
Contributions are more than welcomed, but respect the process:
- Always open an issue first: PR without issue won't be accepted and might even be closed immediatly. The issue is here to discuss the needs and proposals and serves as an history. Try to be as explicit as possible and provide links/screenshots when possible. NOTE: You can open an issue even if you are not the one that will implement the feature/bug fix.
- You can start opening a PR once the issue got approved. Please, immediatly reference the issue on your PR so that people knows the issue is being handled.
Don't forget that this module is not meant for your own personal usage, but for everyone's. For features not implementing strictly the RFC, we might split it in an optional feature of the module.
Metadata
Release files for dnstoolbox 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dnstoolbox-0.1.0.tar.gz | 18.3 kB | Without provenance | Details for dnstoolbox-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dnstoolbox-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dnstoolbox-0.1.0-py3-none-any.whl |
Total release size: 41.7 kB
Release files / dnstoolbox-0.1.0.tar.gz
| Download URL | dnstoolbox-0.1.0.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
220631b27e9d741eb02aeda1ff83bcb26e74e56cc0318716f524e974c8c4418f
|
|
BLAKE2b-256 checksum How to use checksums |
5571136ec65131dbacf2e85e39ff97e1bedd0eb94f9208405ca89c784204f41e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.18
|
Release files / dnstoolbox-0.1.0-py3-none-any.whl
| Download URL | dnstoolbox-0.1.0-py3-none-any.whl |
|---|---|
| Size | 23.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29c90b94fc2b4ae15b47e2b7a680cfd095318e7ce25480be4c7870da4824f369
|
|
BLAKE2b-256 checksum How to use checksums |
b4c8d13767a1429f56413b9c52295858cbe62428147550bd8b0606864d64e5cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.18
|
Security for dnstoolbox 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.