diff --git a/dnsapi.md b/dnsapi.md
index 40a64a8..13fc607 100644
--- a/dnsapi.md
+++ b/dnsapi.md
@@ -1,33 +1,100 @@
-# How to use DNS API
+# How to use DNS API
If your DNS provider doesn't provide API access, you can use our DNS alias mode:
https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode
-## 1. Cloudflare Option:
+* [1. CloudFlare](#dns_cf)
+* [2. DNSPod.cn Option:](#dns_dp)
+* [4. Use GoDaddy.com domain API to automatically issue cert](#dns_gd)
+* [5. Use PowerDNS embedded API to automatically issue cert](#dns_pdns)
+* [6. Use OVH, Kimsufi, So you Start API to automatically issue cert](#dns_ovh)
+* [7. Use nsupdate to automatically issue cert](#dns_nsupdate)
+* [8. Use LuaDNS domain API](#dns_lua)
+* [9. Use DNSMadeEasy domain API](#dns_me)
+* [10. Use Amazon Route53 domain API](#dns_aws)
+* [11. Use Aliyun domain API to automatically issue cert](#dns_ali)
+* [12. Use ISPConfig 3.1 API](#dns_ispconfig)
+* [13. Use Alwaysdata domain API](#dns_ad)
+* [14. Use Linode domain API](#dns_linode_v4)
+* [15. Use FreeDNS](#dns_freedns)
+* [16. Use cyon.ch](#dns_cyon)
+* [18. Use Gandi LiveDNS API](#dns_gandi_livedns)
+* [19. Use Knot (knsupdate) DNS API to automatically issue cert](#dns_knot)
+* [20. Use DigitalOcean API (native)](#dns_dgon)
+* [21. Use ClouDNS.net API](#dns_cloudns)
+* [22. Use Infoblox API](#dns_infoblox)
+* [23. Use VSCALE API](#dns_vscale)
+* [24. Use Dynu API](#dns_dynu)
+* [25. Use DNSimple API](#dns_dnsimple)
+* [26. Use NS1.com API](#dns_nsone)
+* [27. Use DuckDNS.org API](#dns_duckdns)
+* [28. Use Name.com API](#dns_namecom)
+* [29. Use Dyn Managed DNS API to automatically issue cert](#dns_dyn)
+* [30. Use pdd.yandex.ru API](#dns_yandex)
+* [31. Use Hurricane Electric](#dns_he)
+* [33. Use INWX](#dns_inwx)
+* [35. Use Namesilo.com API](#dns_namesilo)
+* [36. Use autoDNS (InternetX)](#dns_autodns)
+* [37. Use Azure DNS](#dns_azure)
+* [38. Use selectel.com(selectel.ru) domain API to automatically issue cert](#dns_selectel)
+* [39. Use zonomi.com domain API to automatically issue cert](#dns_zonomi)
+* [40. Use DreamHost DNS API](#dns_dreamhost)
+* [41. Use DirectAdmin API](#dns_da)
+* [42. Use KingHost DNS API](#dns_zilore)
+* [43. Use Zilore DNS API](#dns_zilore)
+* [44. Use Loopia API](#dns_loopia)
+* [45. Use ACME DNS API](#dns_acmedns)
+* [47. Use Euserv.eu API](#dns_euserv)
+* [48. Use DNSPod.com domain API to automatically issue cert](#dns_gcloud)
+* [50. Use ConoHa API](#dns_netcup)
+* [53. Use Namecheap](#dns_namecheap)
+* [54. Use MyDNS.JP API](#dns_mydnsjp)
+* [55. Use hosting.de API](#dns_hostingde)
+* [56. Use Neodigit.net API](#dns_neodigit)
+* [57. Use Exoscale API](#dns_exoscale)
+* [58. Using PointHQ API to issue certs](#dns_pointhq)
+* [59. Use Active24 API](#dns_active24)
+* [60. Use do.de API](#dns_doapi)
+* [61. Use Nexcess API](#dns_nw)
+* [62. Use Thermo.io API](#dns_nw)
+* [63. Use Futurehosting API](#dns_nw)
+* [65. Use Online API](#dns_online)
+* [66. Use MyDevil.net](#dns_mydevil)
+* [67. Use Core-Networks API to automatically issue cert](#dns_cn)
+* [70. Use UltraDNS API](#dns_ultra)
+* [71. Use deSEC.io](#dns_desec)
+* [72. Use OpenProvider API](#dns_openprovider)
+* [73. Use MaraDNS API](#dns_maradns)
+* [74. Use Hetzner API](#dns_hetzner)
+* [75. Use DDNSS.de API](#dns_ddnss)
+* [76. Use NLnetLabs NSD](#dns_nsd)
+
+
+## 1. CloudFlare Option:
Cloudflare Domain API offers two methods to automatically issue certs.
### Using the global API key
-First you need to login to your Cloudflare account to get your [API key](https://dash.cloudflare.com/profile). Each token generated is not stored on cloudflare account and will have expiry if not set correctly. You will get this in API keys section.
+First you need to login to your Cloudflare account to get your [API key](https://dash.cloudflare.com/profile). Each token generated is not stored on cloudflare account and will have expiry if not set correctly. You will get this in API keys section.
```sh
-export CF_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export CF_Email="xxxx@sss.com"
+export CF_Key=""
+export CF_Email=""
```
-### Using the new cloudflare api token, you will get this after normal login and scroll down on dashboard and copy credentials.
+### Using the new cloudflare api token, you will get this after normal login and scroll down on dashboard and copy credentials.
```sh
-export CF_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export CF_Account_ID="xxxxxxxxxxxxx"
+export CF_Token=""
+export CF_Account_ID=""
```
In order to use the new token, the token currently needs access read access to Zone.Zone, and write access to Zone.DNS, across all Zones. See [Issue #2398](https://github.com/Neilpang/acme.sh/issues/2398) for more info.
Alternatively, if the certificate only covers a single zone, you can restrict the API Token only for write access to Zone.DNS for a single domain, and then specify the `CF_Zone_ID` directly:
```sh
-export CF_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export CF_Account_ID="xxxxxxxxxxxxx"
-export CF_Zone_ID="xxxxxxxxxxxxx"
+export CF_Token=""
+export CF_Account_ID=""
+export CF_Zone_ID=""
```
Ok, let's issue a cert now:
@@ -37,13 +104,15 @@ Ok, let's issue a cert now:
The `CF_Key` and `CF_Email` or `CF_Token`and `CF_Account_ID`will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 2. DNSPod.cn Option:
The DNSPod.cn Domain API option requires that you first login to your account to get a DNSPod API Key and ID.
```sh
-export DP_Id="1234"
-export DP_Key="sADDsdasdgdsf"
+export DP_Id=""
+export DP_Key=""
```
Ok, let's issue a cert now:
@@ -54,12 +123,12 @@ Ok, let's issue a cert now:
The `DP_Id` and `DP_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
-## 3. Use CloudXNS.com domain API to automatically issue cert
+## 3. CloudXNS.com
~~Removed~~
-
+
## 4. Use GoDaddy.com domain API to automatically issue cert
First you need to login to your GoDaddy account to get your API Key and Secret.
@@ -69,8 +138,8 @@ https://developer.godaddy.com/keys/
Please create a Production key, instead of a Test key.
```sh
-export GD_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export GD_Secret="asdfsdafdsfdsfdsfdsfdsafd"
+export GD_Key=""
+export GD_Secret=""
```
Ok, let's issue a cert now:
@@ -81,6 +150,7 @@ Ok, let's issue a cert now:
The `GD_Key` and `GD_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 5. Use PowerDNS embedded API to automatically issue cert
First you need to login to your PowerDNS account to enable the API and set your API-Token in the configuration.
@@ -102,11 +172,13 @@ Ok, let's issue a cert now:
The `PDNS_Url`, `PDNS_ServerId`, `PDNS_Token` and `PDNS_Ttl` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 6. Use OVH, Kimsufi, So you Start API to automatically issue cert
https://github.com/Neilpang/acme.sh/wiki/How-to-use-OVH-domain-api
+
## 7. Use nsupdate to automatically issue cert
First, generate a key for updating the zone
@@ -174,13 +246,14 @@ Ok, let's issue a cert now:
The `NSUPDATE_SERVER`, `NSUPDATE_KEY`, and `NSUPDATE_ZONE` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 8. Use LuaDNS domain API
Get your API token at https://api.luadns.com/settings
```sh
-export LUA_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export LUA_Email="xxxx@sss.com"
+export LUA_Key=""
+export LUA_Email="youremail@example.com"
```
To issue a cert:
@@ -190,13 +263,15 @@ To issue a cert:
The `LUA_Key` and `LUA_Email` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 9. Use DNSMadeEasy domain API
Get your API credentials at https://cp.dnsmadeeasy.com/account/info
```sh
-export ME_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export ME_Secret="qdfqsdfkjdskfj"
+export ME_Key=""
+export ME_Secret=""
```
To issue a cert:
@@ -207,13 +282,14 @@ To issue a cert:
The `ME_Key` and `ME_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 10. Use Amazon Route53 domain API
https://github.com/Neilpang/acme.sh/wiki/How-to-use-Amazon-Route53-API
```sh
-export AWS_ACCESS_KEY_ID=XXXXXXXXXX
-export AWS_SECRET_ACCESS_KEY=XXXXXXXXXXXXXXX
+export AWS_ACCESS_KEY_ID=""
+export AWS_SECRET_ACCESS_KEY=""
```
To issue a cert:
@@ -229,14 +305,16 @@ export AWS_DNS_SLOWRATE=1 (sleep between API requests in seconds)
The `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_DNS_SLOWRATE` will be saved in `~/.acme.sh/account.conf` and will be reused when needed. The `AWS_DNS_SLOWRATE` will enable the sleep between API requests to AWS servers. It will help to mitigate the AWS rate limit
+
+
## 11. Use Aliyun domain API to automatically issue cert
First you need to login to your Aliyun account to get your RAM API key.
[https://ram.console.aliyun.com/users](https://ram.console.aliyun.com/users)
```sh
-export Ali_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export Ali_Secret="jlsdflanljkljlfdsaklkjflsa"
+export Ali_Key=""
+export Ali_Secret=""
```
Ok, let's issue a cert now:
@@ -246,6 +324,8 @@ Ok, let's issue a cert now:
The `Ali_Key` and `Ali_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 12. Use ISPConfig 3.1 API
This only works for ISPConfig 3.1 (and newer).
@@ -268,12 +348,14 @@ To issue a cert:
The `ISPC_User`, `ISPC_Password`, `ISPC_Api`and `ISPC_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 13. Use Alwaysdata domain API
First you need to login to your Alwaysdata account to get your API Key.
```sh
-export AD_API_KEY="myalwaysdataapikey"
+export AD_API_KEY=""
```
Ok, let's issue a cert now:
@@ -285,6 +367,8 @@ Ok, let's issue a cert now:
The `AD_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused
when needed.
+
+
## 14. Use Linode domain API
### Cloud Manager ###
@@ -293,10 +377,10 @@ Cloud Manager: https://cloud.linode.com/profile/tokens
First you need to login to your Linode account to get your API Key.
- 1. Click on "Add a Personal Access Token".
- 2. Give the new key a "Label" (we recommend *ACME*)
- 3. Give it Read/Write access to "Domains"
- 4. "Submit" and copy the new key into the `LINODE_V4_API_KEY` command below.
+1. Click on "Add a Personal Access Token".
+2. Give the new key a "Label" (we recommend *ACME*)
+3. Give it Read/Write access to "Domains"
+4. "Submit" and copy the new key into the `LINODE_V4_API_KEY` command below.
```sh
export LINODE_V4_API_KEY="..."
@@ -314,9 +398,11 @@ Ok, let's issue a cert now:
The `LINODE_V4_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be
reused when needed.
+
+
## 15. Use FreeDNS
-FreeDNS (https://freedns.afraid.org/) does not provide an API to update DNS records (other than IPv4 and IPv6
+[FreeDNS](https://freedns.afraid.org/) does not provide an API to update DNS records (other than IPv4 and IPv6
dynamic DNS addresses). The acme.sh plugin therefore retrieves and updates domain TXT records by logging
into the FreeDNS website to read the HTML and posting updates as HTTP. The plugin needs to know your
userid and password for the FreeDNS website.
@@ -344,6 +430,8 @@ validate with acme.sh at FreeDNS.
If you have any issues with FreeDNS API please report them here...
https://github.com/Neilpang/acme.sh/issues/2305
+
+
## 16. Use cyon.ch
You only need to set your cyon.ch login credentials.
@@ -362,16 +450,19 @@ To issue a cert:
The `CY_Username`, `CY_Password` and `CY_OTP_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 17. Use Domain-Offensive/Resellerinterface/Domainrobot API
~~Removed~~
+
+
## 18. Use Gandi LiveDNS API
-You must enable the new Gandi LiveDNS API first and the create your api key, See: https://api.gandi.net/docs/livedns/
+You must enable the new Gandi LiveDNS API first and then create your api key, See: https://api.gandi.net/docs/livedns/
```sh
-export GANDI_LIVEDNS_KEY="fdmlfsdklmfdkmqsdfk"
+export GANDI_LIVEDNS_KEY=""
```
Ok, let's issue a cert now:
@@ -379,6 +470,8 @@ Ok, let's issue a cert now:
./acme.sh --issue --dns dns_gandi_livedns -d example.com -d www.example.com
```
+
+
## 19. Use Knot (knsupdate) DNS API to automatically issue cert
First, generate a TSIG key for updating the zone.
@@ -430,12 +523,14 @@ Ok, let's issue a cert now:
The `KNOT_SERVER` and `KNOT_KEY` and `KNOT_ZONE` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 20. Use DigitalOcean API (native)
You need to obtain a read and write capable API key from your DigitalOcean account. See: https://www.digitalocean.com/help/api/
```sh
-export DO_API_KEY="75310dc4ca779ac39a19f6355db573b49ce92ae126553ebd61ac3a3ae34834cc"
+export DO_API_KEY=""
```
Ok, let's issue a cert now:
@@ -443,16 +538,18 @@ Ok, let's issue a cert now:
./acme.sh --issue --dns dns_dgon -d example.com -d www.example.com
```
+
+
## 21. Use ClouDNS.net API
You need to set the HTTP API user ID and password credentials. See: https://www.cloudns.net/wiki/article/42/. For security reasons, it's recommended to use a sub user ID that only has access to the necessary zones, as a regular API user has access to your entire account.
```sh
# Use this for a sub auth ID
-export CLOUDNS_SUB_AUTH_ID=XXXXX
+export CLOUDNS_SUB_AUTH_ID=""
# Use this for a regular auth ID
-#export CLOUDNS_AUTH_ID=XXXXX
-export CLOUDNS_AUTH_PASSWORD="YYYYYYYYY"
+#export CLOUDNS_AUTH_ID="Auth ID"
+export CLOUDNS_AUTH_PASSWORD=""
```
Ok, let's issue a cert now:
@@ -461,6 +558,8 @@ Ok, let's issue a cert now:
```
The `CLOUDNS_AUTH_ID` and `CLOUDNS_AUTH_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 22. Use Infoblox API
First you need to create/obtain API credentials on your Infoblox appliance.
@@ -479,12 +578,13 @@ Note: This script will automatically create and delete the ephemeral txt record.
The `Infoblox_Creds` and `Infoblox_Server` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 23. Use VSCALE API
First you need to create/obtain API tokens on your [settings panel](https://vscale.io/panel/settings/tokens/).
```sh
-export VSCALE_API_KEY="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export VSCALE_API_KEY=""
```
Ok, let's issue a cert now:
@@ -492,13 +592,15 @@ Ok, let's issue a cert now:
./acme.sh --issue --dns dns_vscale -d example.com -d www.example.com
```
+
+
## 24. Use Dynu API
First you need to create/obtain API credentials from your Dynu account. See: https://www.dynu.com/resources/api/documentation
```sh
-export Dynu_ClientId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
-export Dynu_Secret=yyyyyyyyyyyyyyyyyyyyyyyyy
+export Dynu_ClientId=""
+export Dynu_Secret=""
```
Ok, let's issue a cert now:
@@ -508,6 +610,8 @@ Ok, let's issue a cert now:
The `Dynu_ClientId` and `Dynu_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 25. Use DNSimple API
First you need to login to your DNSimple account and generate a new oauth token.
@@ -519,7 +623,7 @@ needed to infer the `account_id` used in requests. A user token will not be able
to determine the correct account to use.
```sh
-export DNSimple_OAUTH_TOKEN="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export DNSimple_OAUTH_TOKEN=""
```
To issue the cert just specify the `dns_dnsimple` API.
@@ -534,10 +638,12 @@ be reused when needed.
If you have any issues with this integration please report them to
https://github.com/pho3nixf1re/acme.sh/issues.
+
+
## 26. Use NS1.com API
```sh
-export NS1_Key="fdmlfsdklmfdkmqsdfk"
+export NS1_Key=""
```
Ok, let's issue a cert now:
@@ -545,10 +651,12 @@ Ok, let's issue a cert now:
./acme.sh --issue --dns dns_nsone -d example.com -d www.example.com
```
+
+
## 27. Use DuckDNS.org API
```sh
-export DuckDNS_Token="aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"
+export DuckDNS_Token=""
```
Please note that since DuckDNS uses StartSSL as their cert provider, thus
@@ -557,6 +665,8 @@ Please note that since DuckDNS uses StartSSL as their cert provider, thus
acme.sh --insecure --issue --dns dns_duckdns -d mydomain.duckdns.org
```
+
+
## 28. Use Name.com API
Create your API token here: https://www.name.com/account/settings/api
@@ -564,8 +674,8 @@ Create your API token here: https://www.name.com/account/settings/api
Note: `Namecom_Username` should be your Name.com username and not the token name. If you accidentally run the script with the token name as the username see `~/.acme.sh/account.conf` to fix the issue
```sh
-export Namecom_Username="testuser"
-export Namecom_Token="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+export Namecom_Username=""
+export Namecom_Token=""
```
And now you can issue certs with:
@@ -577,6 +687,8 @@ If you had Two-step Authentication enabled, make sure to change your security se
For issues, please report to https://github.com/raidenii/acme.sh/issues.
+
+
## 29. Use Dyn Managed DNS API to automatically issue cert
First, login to your Dyn Managed DNS account: https://portal.dynect.net/login/
@@ -597,9 +709,9 @@ ZonePublish
Pass the API user credentials to the environment:
```sh
-export DYN_Customer="customer"
-export DYN_Username="apiuser"
-export DYN_Password="secret"
+export DYN_Customer=""
+export DYN_Username=""
+export DYN_Password=""
```
Ok, let's issue a cert now:
@@ -609,10 +721,12 @@ Ok, let's issue a cert now:
The `DYN_Customer`, `DYN_Username` and `DYN_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 30. Use pdd.yandex.ru API
```sh
-export PDD_Token="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+export PDD_Token=""
```
Follow these instructions to get the token for your domain https://tech.yandex.com/domain/doc/concepts/access-docpage/
@@ -624,13 +738,15 @@ Sometimes cloudflare / google doesn't pick new dns records fast enough. You can
For issues, please report to https://github.com/non7top/acme.sh/issues.
+
+
## 31. Use Hurricane Electric
-Hurricane Electric (https://dns.he.net/) doesn't have an API so just set your login credentials like so:
+[Hurricane Electric he.net](https://dns.he.net/) doesn't have an API so just set your login credentials like so:
```sh
-export HE_Username="yourusername"
-export HE_Password="password"
+export HE_Username=""
+export HE_Password=""
```
Then you can issue your certificate:
@@ -643,12 +759,13 @@ The `HE_Username` and `HE_Password` settings will be saved in `~/.acme.sh/accoun
Please report any issues to https://github.com/angel333/acme.sh or to .
-## 32. Use UnoEuro API to automatically issue cert
+## 32. Use UnoEuro API to automatically issue cert
+**UPD** The UnoEuro is now Simple.com
First you need to login to your UnoEuro account to get your API key.
```sh
-export UNO_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export UNO_Key=""
export UNO_User="UExxxxxx"
```
@@ -659,13 +776,15 @@ Ok, let's issue a cert now:
The `UNO_Key` and `UNO_User` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 33. Use INWX
-[INWX](https://www.inwx.de/) offers an [xmlrpc api](https://www.inwx.de/de/help/apidoc) with your standard login credentials, set them like so:
+[INWX.de](https://www.inwx.de/) offers a [xmlrpc api](https://www.inwx.de/de/help/apidoc) with your standard login credentials, set them like so:
```sh
-export INWX_User="yourusername"
-export INWX_Password="password"
+export INWX_User=""
+export INWX_Password=""
```
Then you can issue your certificates with:
@@ -679,18 +798,18 @@ The `INWX_User` and `INWX_Password` settings will be saved in `~/.acme.sh/accoun
If your account is secured by mobile tan you have also defined the shared secret.
```sh
-export INWX_Shared_Secret="shared secret"
+export INWX_Shared_Secret=""
```
You may need to re-enable the mobile tan to gain the shared secret.
## 34. User Servercow API v1
-Create a new user from the servercow control center. Don't forget to activate **DNS API** for this user.
+Create a new user from the Servercow control center. Don't forget to activate **DNS API** for this user.
```sh
-export SERVERCOW_API_Username=username
-export SERVERCOW_API_Password=password
+export SERVERCOW_API_Username=""
+export SERVERCOW_API_Password=""
```
Now you cann issue a cert:
@@ -700,13 +819,15 @@ Now you cann issue a cert:
```
Both, `SERVERCOW_API_Username` and `SERVERCOW_API_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 35. Use Namesilo.com API
You'll need to generate an API key at https://www.namesilo.com/account/api-manager
Optionally you may restrict the access to an IP range there.
```sh
-export Namesilo_Key="xxxxxxxxxxxxxxxxxxxxxxxx"
+export Namesilo_Key=""
```
And now you can issue certs with:
@@ -715,9 +836,10 @@ And now you can issue certs with:
./acme.sh --issue --dns dns_namesilo --dnssleep 900 -d example.com -d www.example.com
```
+
## 36. Use autoDNS (InternetX)
-[InternetX](https://www.internetx.com/) offers an [xml api](https://help.internetx.com/display/API/AutoDNS+XML-API) with your standard login credentials, set them like so:
+[InternetX](https://www.internetx.com/) offers a [xml api](https://help.internetx.com/display/API/AutoDNS+XML-API) with your standard login credentials, set them like so:
```sh
export AUTODNS_USER="yourusername"
@@ -733,15 +855,17 @@ Then you can issue your certificates with:
The `AUTODNS_USER`, `AUTODNS_PASSWORD` and `AUTODNS_CONTEXT` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 37. Use Azure DNS
You have to create a service principal first. See:[How to use Azure DNS](https://github.com/acmesh-official/acme.sh/wiki/How-to-use-Azure-DNS)
```sh
-export AZUREDNS_SUBSCRIPTIONID="12345678-9abc-def0-1234-567890abcdef"
-export AZUREDNS_TENANTID="11111111-2222-3333-4444-555555555555"
-export AZUREDNS_APPID="3b5033b5-7a66-43a5-b3b9-a36b9e7c25ed"
-export AZUREDNS_CLIENTSECRET="1b0224ef-34d4-5af9-110f-77f527d561bd"
+export AZUREDNS_SUBSCRIPTIONID=""
+export AZUREDNS_TENANTID=""
+export AZUREDNS_APPID=""
+export AZUREDNS_CLIENTSECRET=""
```
Then you can issue your certificates with:
@@ -764,12 +888,14 @@ Before running acme.sh following variables need to bo set:
Issuing certificates using managed identity clears previously set settings: `AZUREDNS_TENANTID`, `AZUREDNS_APPID`, `AZUREDNS_CLIENTSECRET`.
`AZUREDNS_SUBSCRIPTIONID` and `AZUREDNS_MANAGEDIDENTITY` will be saved in ~/.acme.sh/account.conf for future use.
+
+
## 38. Use selectel.com(selectel.ru) domain API to automatically issue cert
First you need to login to your account to get your API key from: https://my.selectel.ru/profile/apikeys.
```sh
-export SL_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export SL_Key=""
```
@@ -780,6 +906,8 @@ Ok, let's issue a cert now:
The `SL_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 39. Use zonomi.com domain API to automatically issue cert
First you need to login to your account to find your API key from: http://zonomi.com/app/dns/dyndns.jsp
@@ -791,7 +919,7 @@ https://zonomi.com/app/dns/dyndns.jsp?host=example.com&api_key=10633645589435409
```
```sh
-export ZM_Key="1063364558943540954358668888888888"
+export ZM_Key=""
```
@@ -802,6 +930,8 @@ Ok, let's issue a cert now:
The `ZM_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 40. Use DreamHost DNS API
DNS API keys may be created at https://panel.dreamhost.com/?tree=home.api.
@@ -815,13 +945,15 @@ export DH_API_KEY=""
The 'DH_API_KEY' will be saved in `~/.acme.sh/account.conf` and will
be reused when needed.
+
+
## 41. Use DirectAdmin API
-The DirectAdmin interface has it's own Let's encrypt functionality, but this
+The DirectAdmin interface has its own Let's encrypt functionality, but this
script can be used to generate certificates for names which are not hosted on
DirectAdmin
User must provide login data and URL to the DirectAdmin incl. port.
-You can create an user which only has access to
+You can create a user which only has access to
- CMD_API_DNS_CONTROL
- CMD_API_SHOW_DOMAINS
@@ -842,6 +974,8 @@ Ok, let's issue a cert now:
The `DA_Api` and `DA_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 42. Use KingHost DNS API
API access must be enabled at https://painel.kinghost.com.br/painel.api.php
@@ -854,12 +988,14 @@ export KINGHOST_Password="yourpassword"
The `KINGHOST_username` and `KINGHOST_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 43. Use Zilore DNS API
First, get your API key at https://my.zilore.com/account/api
```sh
-export Zilore_Key="5dcad3a2-36cb-50e8-cb92-000002f9"
+export Zilore_Key=""
```
Ok, let's issue a cert now:
@@ -869,6 +1005,7 @@ Ok, let's issue a cert now:
The `Zilore_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 44. Use Loopia API
User must provide login credentials to the Loopia API.
@@ -906,12 +1043,14 @@ And to issue a cert run:
The exported variables will be saved in `~/.acme.sh/account.conf` and
will be reused when needed.
+
+
## 45. Use ACME DNS API
ACME DNS is a limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
https://github.com/joohoi/acme-dns
-```
+```sh
# Usage:
# export ACMEDNS_BASE_URL="https://auth.acme-dns.io"
#
@@ -932,14 +1071,16 @@ First you need to login to your TELE3 account to set your API-KEY.
https://www.tele3.cz/system-acme-api.html
```sh
-export TELE3_Key="MS2I4uPPaI..."
-export TELE3_Secret="kjhOIHGJKHg"
+export TELE3_Key=""
+export TELE3_Secret=""
./acme.sh --issue --dns dns_tele3 -d example.com -d *.example.com
```
The TELE3_Key and TELE3_Secret will be saved in ~/.acme.sh/account.conf and will be reused when needed.
+
+
## 47. Use Euserv.eu API
First you need to login to your euserv.eu account and activate your API Administration (API Verwaltung).
@@ -962,13 +1103,15 @@ The `EUSERV_Username` and `EUSERV_Password` will be saved in `~/.acme.sh/account
Please report any issues to https://github.com/initit/acme.sh or to
+
+
## 48. Use DNSPod.com domain API to automatically issue cert
First you need to get your API Key and ID by this [get-the-user-token](https://www.dnspod.com/docs/info.html#get-the-user-token).
```sh
-export DPI_Id="1234"
-export DPI_Key="sADDsdasdgdsf"
+export DPI_Id=""
+export DPI_Key=""
```
Ok, let's issue a cert now:
@@ -999,6 +1142,8 @@ export CLOUDSDK_ACTIVE_CONFIG_NAME=default # see the note above
`dns_gcloud` also supports [DNS alias mode](https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode).
+
+
## 50. Use ConoHa API
First you need to login to your ConoHa account to get your API credentials.
@@ -1032,18 +1177,18 @@ Now, let's issue a cert:
```
The `NC_Apikey`,`NC_Apipw` and `NC_CID` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
## 52. Use GratisDNS.dk
-
-Removed
+Removed
https://github.com/acmesh-official/acme.sh/pull/4049
-
+
## 53. Use Namecheap
-You will need your namecheap username, API KEY (https://www.namecheap.com/support/api/intro.aspx) and your external IP address (or an URL to get it), this IP will need to be whitelisted at Namecheap.
+You will need your namecheap username, API KEY (https://www.namecheap.com/support/api/intro.aspx) and your external IP address (or a URL to get it), this IP will need to be whitelisted at Namecheap.
Due to Namecheap's API limitation all the records of your domain will be read and re applied, make sure to have a backup of your records you could apply if any issue would arise.
```sh
@@ -1052,7 +1197,7 @@ export NAMECHEAP_API_KEY="..."
export NAMECHEAP_SOURCEIP="..."
```
-NAMECHEAP_SOURCEIP can either be an IP address or an URL to provide it (e.g. https://ifconfig.co/ip).
+NAMECHEAP_SOURCEIP can either be an IP address or a URL to provide it (e.g. https://ifconfig.co/ip).
The username and password will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1064,13 +1209,15 @@ Now you can issue a certificate.
If you find any bugs of namecheap dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2107
+
+
## 54. Use MyDNS.JP API
First, register to MyDNS.JP and get MasterID and Password.
```sh
-export MYDNSJP_MasterID=MasterID
-export MYDNSJP_Password=Password
+export MYDNSJP_MasterID=""
+export MYDNSJP_Password=""
```
To issue a certificate:
@@ -1080,6 +1227,8 @@ To issue a certificate:
```
The `MYDNSJP_MasterID` and `MYDNSJP_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 55. Use hosting.de API
Create an API key in your hosting.de account here: https://secure.hosting.de
@@ -1104,10 +1253,12 @@ Ok, let's issue a cert now:
The hosting.de API key and endpoint will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 56. Use Neodigit.net API
```sh
-export NEODIGIT_API_TOKEN="eXJxTkdUVUZmcHQ3QWJackQ4ZGlMejRDSklRYmo5VG5zcFFKK2thYnE0WnVnNnMy"
+export NEODIGIT_API_TOKEN=""
```
Ok, let's issue a cert now:
@@ -1117,6 +1268,8 @@ Ok, let's issue a cert now:
Neodigit API Token will be saved in `~/.acme.sh/account.conf` and will be used when needed.
+
+
## 57. Use Exoscale API
Create an API key and secret key in the Exoscale account section
@@ -1124,8 +1277,8 @@ Create an API key and secret key in the Exoscale account section
Set your API and secret key:
```sh
-export EXOSCALE_API_KEY='xxx'
-export EXOSCALE_SECRET_KEY='xxx'
+export EXOSCALE_API_KEY=''
+export EXOSCALE_SECRET_KEY=''
```
Now, let's issue a cert:
@@ -1135,18 +1288,24 @@ Now, let's issue a cert:
The `EXOSCALE_API_KEY` and `EXOSCALE_SECRET_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 58. Using PointHQ API to issue certs
Log into [PointHQ account management](https://app.pointhq.com/profile) and copy the API key from the page there.
-```export PointHQ_Key="apikeystringgoeshere"
+```
+export PointHQ_Key="apikeystringgoeshere"
exportPointHQ_Email="accountemail@yourdomain.com"
```
You can then issue certs by using:
-```./acme.sh --issue --dns dns_pointhq -d example.com -d www.example.com
+```
+./acme.sh --issue --dns dns_pointhq -d example.com -d www.example.com
```
+
+
## 59. Use Active24 API
Create an API token in the Active24 account section, documentation on https://faq.active24.com/cz/790131-REST-API-rozhran%C3%AD.
@@ -1154,7 +1313,7 @@ Create an API token in the Active24 account section, documentation on https://fa
Set your API token:
```sh
-export ACTIVE24_Token='xxx'
+export ACTIVE24_Token=''
```
Now, let's issue a cert, set `dnssleep` for propagation new DNS record:
@@ -1164,13 +1323,15 @@ Now, let's issue a cert, set `dnssleep` for propagation new DNS record:
The `ACTIVE24_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 60. Use do.de API
Create an API token in your do.de account ([Create token here](https://www.do.de/account/letsencrypt/) | [Documentation](https://www.do.de/wiki/LetsEncrypt_-_Entwickler)).
Set your API token:
```sh
-export DO_LETOKEN='FmD408PdqT1E269gUK57'
+export DO_LETOKEN=""
```
To issue a certificate run:
@@ -1180,11 +1341,13 @@ To issue a certificate run:
The API token will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 61. Use Nexcess API
First, you'll need to login to the [Nexcess.net Client Portal](https://portal.nexcess.net) and [generate a new API token](https://portal.nexcess.net/api-token).
-Once you have a token, set it in your systems environment:
+Once you have a token, set it in your system's environment:
```sh
export NW_API_TOKEN="YOUR_TOKEN_HERE"
@@ -1201,11 +1364,13 @@ The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.co
If you find any bugs of Nexcess dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2088
+
+
## 62. Use Thermo.io API
First, you'll need to login to the [Thermo.io Client Portal](https://core.thermo.io) and [generate a new API token](https://core.thermo.io/api-token).
-Once you have a token, set it in your systems environment:
+Once you have a token, set it in your system's environment:
```sh
export NW_API_TOKEN="YOUR_TOKEN_HERE"
@@ -1220,14 +1385,16 @@ Finally, we'll issue the certificate: (Thermo DNS publishes at max every 15 minu
The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+
+
## 63. Use Futurehosting API
First, you'll need to login to the [Futurehosting Client Portal](https://my.futurehosting.com) and [generate a new API token](https://my.futurehosting.com/api-token).
-Once you have a token, set it in your systems environment:
+Once you have a token, set it in your system's environment:
```sh
-export NW_API_TOKEN="YOUR_TOKEN_HERE"
+export NW_API_TOKEN=""
export NW_API_ENDPOINT="https://my.futurehosting.com"
```
@@ -1244,8 +1411,8 @@ The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.co
Set username and API key, which is available under "My Profile & Settings"
```sh
-export RACKSPACE_Username='username'
-export RACKSPACE_Apikey='xxx'
+export RACKSPACE_Username=""
+export RACKSPACE_Apikey=""
```
Now, let's issue a cert:
@@ -1256,12 +1423,14 @@ Now, let's issue a cert:
If you find any bugs of Rackspace dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2091
+
+
## 65. Use Online API
First, you'll need to retrive your API key, which is available under https://console.online.net/en/api/access
```sh
-export ONLINE_API_KEY='xxx'
+export ONLINE_API_KEY=''
```
To issue a cert run:
@@ -1274,6 +1443,8 @@ To issue a cert run:
If you find any bugs of online.net dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2093
+
+
## 66. Use MyDevil.net
Make sure that you can execute own binaries:
@@ -1294,14 +1465,16 @@ To issue a new certificate, run:
After certificate is ready, you can install it with [deploy command](https://github.com/Neilpang/acme.sh/wiki/deployhooks#14-deploy-your-cert-on-mydevilnet).
+
+
## 67. Use Core-Networks API to automatically issue cert
-First you need to login to your Core-Networks account to to set up an API-User.
+First you need to login to your Core-Networks account to set up an API-User.
Then export username and password to use these credentials.
```sh
-export CN_User="user"
-export CN_Password="passowrd"
+export CN_User=""
+export CN_Password=""
```
Ok, let's issue a cert now:
@@ -1350,7 +1523,7 @@ To issue a cert run:
If you find any bugs of zone.eu (zone.ee) dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2146
-
+
## 70. Use UltraDNS API
UltraDNS is a paid for service that provides DNS, as well as Web and Mail forwarding (as well as reporting, auditing, and advanced tools).
@@ -1359,13 +1532,13 @@ More information can be found here: https://www.security.neustar/lp/ultra20/inde
The REST API documentation for this service is found here: https://portal.ultradns.com/static/docs/REST-API_User_Guide.pdf
-Set your UltraDNS User name, and password; these would be the same you would use here:
+Set your UltraDNS username, and password; these would be the same you would use here:
https://portal.ultradns.com/ - or if you create an API only user, that username and password would be better utilized.
```sh
-export ULTRA_USR="abcd"
-export ULTRA_PWD="efgh"
+export ULTRA_USR=""
+export ULTRA_PWD=""
To issue a cert run:
@@ -1374,13 +1547,14 @@ To issue a cert run:
`ULTRA_USR` and `ULTRA_PWD` will be saved in `~/.acme.sh/account.conf` and will be resued when needed.
+
## 71. Use deSEC.io
Sign up for dynDNS at https://desec.io first.
Set your API token (password) by generating one from your account on desec.io (it's also a good idea to restrict the IPv4 / IPv6 address(es) it can be used from).
```sh
-export DEDYN_TOKEN=d41d8cd98f00b204e9800998ecf8427e
+export DEDYN_TOKEN=""
```
To issue a certificate run:
```sh
@@ -1390,14 +1564,14 @@ To issue a certificate run:
If you find any bugs of deSEC.io API, please report here: https://github.com/Neilpang/acme.sh/issues/2180
-## 72. Use OpenProvider API
+## 72. Use OpenProvider API
First, you need to enable API access and retrieve your password hash on https://rcp.openprovider.eu/account/dashboard.php
```sh
-export OPENPROVIDER_USER='username'
-export OPENPROVIDER_PASSWORDHASH='xxx'
+export OPENPROVIDER_USER=""
+export OPENPROVIDER_PASSWORDHASH=""
./acme.sh --issue --dns dns_openprovider -d example.com -d www.example.com
```
@@ -1406,8 +1580,8 @@ export OPENPROVIDER_PASSWORDHASH='xxx'
If you find any bugs of OpenProvider dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2104
-## 73. Use MaraDNS API
+## 73. Use MaraDNS API
Make sure you've configured MaraDNS properly and setup a zone file for your domain. See [`csv2(5)`](https://manpages.debian.org/stretch/maradns/csv2.5.en.html).
@@ -1430,8 +1604,8 @@ Issuing a certificate:
If you find any bugs of MaraDNS DNS API, please report here: https://github.com/Neilpang/acme.sh/issues/2072
-## 74. Use Hetzner API
+## 74. Use Hetzner API
Get the API Token:
Use [dnsConsole](https://dns.hetzner.com/) to create your hetzner api token.
@@ -1442,8 +1616,8 @@ export HETZNER_Token=""
./acme.sh --issue --dns dns_hetzner -d example.com -d www.example.com --server letsencrypt
```
-## 75. Use DDNSS.de API
+## 75. Use DDNSS.de API
First create an account at https://ddnss.de. After that create a new host record.
In the definition for the host make sure to set the checkbox for "Wildcard" and for "TXT".
@@ -1462,8 +1636,8 @@ After that you can issue a new certificate:
If you find any bugs of ddnss.de API, please report here: https://github.com/Neilpang/acme.sh/issues/2230
-## 76. Use NLnetLabs NSD
+## 76. Use NLnetLabs NSD
You need to export two variables. Your zonefile which the script will automatically edit:
```sh
@@ -1487,9 +1661,6 @@ To issue a new certificate, run:
If you find any bugs of NLnetLabs NSD dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2245
-
-----------------------------------
-**More APIs see here...**
-
-[More APIs](https://github.com/Neilpang/acme.sh/wiki/dnsapi2)
+**[More APIs see here...](https://github.com/Neilpang/acme.sh/wiki/dnsapi2)**