Certbot Domain Chief plugin
This plugin enables DNS verification with Certbot when using Domain Chief.
Installation
If you installed certbot as a snap, then you have to install this plugin as a snap as well:
snap install certbot-dns-domainchief
snap set certbot trust-plugin-with-root=ok
snap connect certbot:plugin certbot-dns-domainchief
and can be upgraded using the refresh command:
snap refresh certbot-dns-domainchief
Alternatively this package can be installed with pip:
pip install certbot-dns-domainchief
and can be upgraded using the --upgrade flag
pip install --upgrade certbot-dns-domainchief
Credentials
You need to supply Certbot with a Domain Chief API key, this is an example of how a credentials file can look:
# Domain Chief API credentials used by Certbot
dns_domainchief_api_key = ctp_...
You can create a new API key here, ensure it has only the domainchief:acme:write scope and has the correct team selected.
The domainchief:acme:write scope only allows publishing and deleting TXT records on _acme-challenge names, it cannot read your domains or change any other DNS record. Keep in mind that the credentials file should still be readable only by the user running Certbot, because anyone holding the key can complete DNS-01 challenges and obtain certificates for the domains in your team.
Examples
Simple example for a single domain:
certbot certonly \
--authenticator dns-domainchief \
--dns-domainchief-credentials ~/.secrets/domainchief.ini \
-d example.com
Simple example for wildcard domain:
certbot certonly \
--authenticator dns-domainchief \
--dns-domainchief-credentials ~/.secrets/domainchief.ini \
-d example.com \
-d *.example.com
Example changing the propagation delay, although you should not have to adjust it normally:
certbot certonly \
--authenticator dns-domainchief \
--dns-domainchief-credentials ~/.secrets/domainchief.ini \
--dns-domainchief-propagation-seconds 120 \
-d example.com
Security Vulnerabilities
If you discover a security vulnerability, please send an e-mail to us at hello@chief.app. All security vulnerabilities will be swiftly addressed.
Metadata
Release files for certbot-dns-domainchief 1.3.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 | |
|---|---|---|---|---|
| certbot_dns_domainchief-1.3.0.tar.gz | 7.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| certbot_dns_domainchief-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / certbot_dns_domainchief-1.3.0.tar.gz
| Download URL | certbot_dns_domainchief-1.3.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bec9e60381d2aa20f1f3fb8c2f42d9f4074e0c92edd69376d3bff3166e2d8d8
|
|
BLAKE2b-256 checksum How to use checksums |
2cf00a6a48f35b34a3c469d2835753eda2bde64f542fda07bb53852ed2f33dc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / certbot_dns_domainchief-1.3.0-py3-none-any.whl
| Download URL | certbot_dns_domainchief-1.3.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cd759f5720a25f7dca8b0406bef52f001775ced1d579eeaba2f954dd3dfbc4f
|
|
BLAKE2b-256 checksum How to use checksums |
e9c3c1375ed8604f4f1034b3941fa9977c36f934991131c1f483913af1a6b56b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for certbot-dns-domainchief 1.3.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.