From 728254ba9a9c985a5a5e524b2eecbda75d52d3b4 Mon Sep 17 00:00:00 2001
From: Sergey Ponomarev <stokito@gmail.com>
Date: Tue, 6 Jun 2023 17:02:25 +0300
Subject: [PATCH] add anchors to make it easier to refer from other places

---
 dnsapi2.md | 575 ++++++++++++++++++++++++++++++++++++++---------------
 1 file changed, 419 insertions(+), 156 deletions(-)

diff --git a/dnsapi2.md b/dnsapi2.md
index 5e9a561..47e825e 100644
--- a/dnsapi2.md
+++ b/dnsapi2.md
@@ -1,6 +1,9 @@
+
+<a name="dns_schlundtech"/>
+
 ## 76. Use Schlundtech
 
-[Schlundtech](https://www.schlundtech.de/) offers an [xml api](https://www.schlundtech.de/services/xml-gateway/)  with your standard login credentials, set them like so:
+[Schlundtech](https://www.schlundtech.de/) offers a [xml api](https://www.schlundtech.de/services/xml-gateway/)  with your standard login credentials, set them like so:
 
 ```sh
 export SCHLUNDTECH_USER="yourusername"
@@ -15,13 +18,17 @@ Then you can issue your certificates with:
 
 The `SCHLUNDTECH_USER` and `SCHLUNDTECH_PASSWORD` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of Schlundtech.de API, please report here: https://github.com/Neilpang/acme.sh/issues/2246
+If you find any bugs of Schlundtech.de API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2246
+
+
+<a name="dns_one"/>
 
 ## 77. Use your one.com credentials as you would login into the control panel.
 
 ```sh
-export ONECOM_User="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export ONECOM_Password="xxxx@sss.com"
+export ONECOM_User="<username>"
+export ONECOM_Password="youremail@example.com"
 ```
 
 Ok, let's issue a cert now:
@@ -30,13 +37,13 @@ Ok, let's issue a cert now:
 ```
 
 Note:
-It's no longer possible to add TXT Records with the Name "_acme-challenge" to the base Domain.  
+It's no longer possible to add TXT Records with the Name `_acme-challenge` to the base Domain.  
 To override the fallback value, you must use a CNAME and proxy it.  
 For example:  
 CNAME _acme-challenge.yourdomain.com => proxy_acme-challenge.yourdomain.com  
 The TXT Records have to be created on proxy_acme-challenge.yourdomain.com  
 Since the default CNAME TTL is 3600 seconds, it is recommended to leave the CNAME record.  
-But if you would like to use the build-in SSL (for your Web-Site etc.) from one.com, you have to delete the Record. 
+But if you would like to use the build-in SSL (for your Web-Site etc.) from one.com, you have to delete the Record.
 
 You can set "ONECOM_KeepCnameProxy" to keep the CNAME record.
 
@@ -48,9 +55,13 @@ By default the CNAME record will be removed.
 
 The `ONECOM_User`,`ONECOM_Password` and `ONECOM_KeepCnameProxy` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of one.com dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2103
+If you find any bugs of one.com dns API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2103
 
-## 78. Use acmeproxy DNS API
+
+<a name="dns_acmeproxy"/>
+
+## 78. Use AcmeProxy DNS API
 
 [Acmeproxy](https://github.com/mdbraber/acmeproxy/) can be used to as a single host in your network to request certificates through a DNS API. Clients can connect with one single host (the acmeproxy) so you don't need to store your DNS API credentials on every single host that wants to request a certificate.
 
@@ -68,7 +79,11 @@ Then you can issue your certificates with:
 
 The `ACMEPROXY_ENDPOINT`, `ACMEPROXY_USERNAME` and `ACMEPROXY_PASSWORD` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of acmeproxy DNS API, please report here: https://github.com/Neilpang/acme.sh/issues/2251
+If you find any bugs of AcmeProxy DNS API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2251
+
+
+<a name="dns_internetbs"/>
 
 ## 79. Use internetbs.net API
 
@@ -87,7 +102,11 @@ To issue a certificate run:
 
 The `INTERNETBS_API_KEY` and `INTERNETBS_API_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of internetbs.net API, please report here: https://github.com/Neilpang/acme.sh/issues/2261
+If you find any bugs of internetbs.net API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2261
+
+
+<a name="dns_durabledns"/>
 
 ## 80. Use durabledns.com API
 
@@ -106,9 +125,12 @@ To issue a certificate run:
 
 The `DD_API_User` and `DD_API_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of durabledns.com API, please report here: https://github.com/Neilpang/acme.sh/issues/2281
+If you find any bugs of durabledns.com API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2281
 
 
+<a name="dns_regru"/>
+
 ## 81. Use reg.ru API
 
 Set your API credentials:
@@ -124,7 +146,8 @@ To issue a certificate run:
 
 The `REGRU_API_Username` and `REGRU_API_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of reg.ru API, please report here: [Issue #2336](../issues/2336)
+If you find any bugs of reg.ru API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2336
 
 RU:
 
@@ -157,7 +180,11 @@ export REGRU_API_Password='водим пароль каторый настрои
 ```
 Настройки для авторизации `REGRU_API_Username` и `REGRU_API_Password` будут сохранены в `~/.acme.sh/account.conf` и будут использоваться повторно при необходимости из конфига acme.
 
-Если вы обнаружите какие-либо ошибки в API reg.ru, сообщите об этом здесь: [Issue #2336](../issues/2336)
+Если вы обнаружите какие-либо ошибки в API reg.ru, сообщите об этом здесь:
+https://github.com/Neilpang/acme.sh/issues/2336
+
+
+<a name="dns_vultr"/>
 
 ## 82. Use Vultr DNS API to automatically issue cert
 
@@ -177,9 +204,11 @@ To issue a cert:
 
 The `VULTR_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs of Vultr API, please report here: [Issue #2374](../../issues/2374)
+If you find any bugs of Vultr API, please report here:
+https://github.com/Neilpang/acme.sh/issues/2374
 
 
+<a name="dns_jd"/>
 
 ## 83. Use jdcloud.com DNS API to automatically issue cert
 
@@ -188,8 +217,8 @@ If you find any bugs of Vultr API, please report here: [Issue #2374](../../issue
 https://uc.jdcloud.com/account/accesskey
 
 ```sh
-export JD_ACCESS_KEY_ID="sdfsdfsdfljlbjkljlkjsdfoiwje"
-export JD_ACCESS_KEY_SECRET="xxxxxxx"
+export JD_ACCESS_KEY_ID="<key id>"
+export JD_ACCESS_KEY_SECRET="<secret>"
 ```
 
 然后生成证书:
@@ -209,6 +238,9 @@ export JD_REGION="cn-north-1" # 这里写你要改的区域
 有 bug 的话可以报到这里: https://github.com/Neilpang/acme.sh/issues/2388
 
 
+
+<a name="dns_hexonet"/>
+
 ## 84. Use hexonet.com DNS API to automatically issue a cert
 
 Create a role user in your Account -> Settings -> ShareAccess
@@ -227,13 +259,12 @@ export Hexonet_Password="role password"
 ```
 
 For example:
-My user name is `neilpang`, my role id is: `testid`. So I use the following format:
+My username is `neilpang`, my role id is: `testid`. So I use the following format:
 
 ```sh
 export Hexonet_Login='neilpang!testid'
 ```
 
-
 To issue a cert:
 
 ```sh
@@ -243,17 +274,19 @@ To issue a cert:
 The `Hexonet_Login` and `Hexonet_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 If you find any bugs, please report here:
-
 https://github.com/Neilpang/acme.sh/issues/2389
 
 
+
+<a name="dns_domeneshop"/>
+
 ## 85. Use Domeneshop DNS API to automatically issue a cert
 
 You'll have to get a Domeneshop API key and secret (https://api.domeneshop.no/docs/).
 
 ```sh
-export DOMENESHOP_Token="1234567890"
-export DOMENESHOP_Secret="1234567890abcdefghijklmnopqrstuvw"
+export DOMENESHOP_Token="<token>"
+export DOMENESHOP_Secret="<secret>"
 ```
 
 Ok, let's issue a cert now:
@@ -264,10 +297,12 @@ Ok, let's issue a cert now:
 The `DOMENESHOP_Token` and `DOMENESHOP_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 If you find any bugs, please report here:
-
 https://github.com/Neilpang/acme.sh/issues/2457
 
 
+
+<a name="dns_opnsense"/>
+
 ## 86. Use OPNsense embedded API to automatically issue cert
 
 First you need to login to your OPNsense account and create an API Key for a user with access to the Bind service.
@@ -290,9 +325,11 @@ Ok, let's issue a cert now:
 The `OPNs_Host`, `OPNs_Port`, `OPNs_Key`, `OPNs_Token` and `OPNs_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 If you find any bugs, please report here:
-
 https://github.com/Neilpang/acme.sh/issues/2480
 
+
+<a name="dns_rcode0"/>
+
 ## 87. Use the RcodeZero API to automatically issue cert
 
 First you need to login to your RcodeZero account, enable the REST API and generate an ACME API token (only the ACME API token will work wih acme.sh. It has limited access and could only be used to add/remove challenges to the zones).
@@ -312,7 +349,7 @@ The `RCODE0_API_TOKEN` will be saved in `~/.acme.sh/account.conf` and will be re
 
 The RcodeZero API driver supports two addtional environment variables
 ```sh
-export RCODE0_URL=https://my.rcodezero.at
+export RCODE0_URL="https://my.rcodezero.at"
 ```
 Use a different RcodeZero API Endpoint (e.g. the RcodeZero Testsystem)
 ```sh
@@ -321,12 +358,16 @@ export RCODE0_TTL=60
 Use a different TTL for the generated records
 
 If you find any bugs, please report here:
-
 https://github.com/Neilpang/acme.sh/issues/2490
 
+
+<a name="dns_miab"/>
+
 ## 88. Use MailinaBox
 
-Use the MailinaBox (MIAB) Custom DNS REST API interface to MIAB DNS. You only need to set your MIAB login credentials and the fully qualified domain name of the MIAB Server. Suggest single quote over double quote to ensure characters are not interpreted by the shell - important for passwords.
+Use the Mail-In-a-Box (MIAB) Custom DNS REST API interface to MIAB DNS.
+You only need to set your MIAB login credentials and the fully qualified domain name of the MIAB Server.
+Suggest single quote over double quote to ensure characters are not interpreted by the shell - important for passwords.
 
 ```sh
 export MIAB_Username='your_MIAB_admin_username'
@@ -342,16 +383,15 @@ To issue a cert:
 The `MIAB_Username`, `MIAB_Password` and `MIAB_Server` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 If you find any bugs, please report here:
-
 https://github.com/Neilpang/acme.sh/issues/2550
 
 
-
+<a name="dns_nic"/>
 
 ## 89. Use nic.ru DNS
 You need to login to nic.ru account and register your application [here](https://www.nic.ru/manager/oauth.cgi?step=oauth.app_register).
 
-You need to define the following environment variables befor issuing a cert: 
+You need to define the following environment variables befor issuing a cert:
 * `NIC_Username` - login for site `nic.ru` in form `000000/NIC-D`
 * `NIC_Password` - password for site `nic.ru`. It may be administrative or technical password ([details](https://www.nic.ru/help/use-of-administrative-and-technical-passwords-according-to-the-agreement_6148.html))
 * `NIC_ClientID` - your application identifier ([details](https://www.nic.ru/help/oauth-server_5809.html))
@@ -372,19 +412,21 @@ To issue a cert:
 The NIC_Username, NIC_Password, NIC_ClientID and NIC_ClientSecret will be saved in ~/.acme.sh/account.conf and will be reused when needed.
 
 If you find any bugs, please report here:
-
 https://github.com/Neilpang/acme.sh/issues/2547
 
-Docs: 
+Docs:
 * https://www.nic.ru/help/upload/file/API_DNS-hosting-en.pdf
 * https://www.nic.ru/help/oauth-server_5809.html
 
+
+<a name="dns_leaseweb"/>
+
 ## 90. Use Leaseweb.com domain API to automatically issue cert
 
 First you need to login to your Leaseweb account to get your API Key.
 
 ```sh
-export LSW_Key="safas-3fs3sd-34sdf-safss"
+export LSW_Key="<key>"
 ```
 
 Ok, let's issue a cert now:
@@ -394,15 +436,19 @@ Ok, let's issue a cert now:
 
 The `LSW_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-If you find any bugs, please report here: https://github.com/Neilpang/acme.sh/issues/2558
+If you find any bugs, please report here:
+https://github.com/Neilpang/acme.sh/issues/2558
 
 
+
+<a name="dns_variomedia"/>
+
 ## 91. Use variomedia.de domain API to automatically issue cert
 
 First you need to obtain your API Key from variomedia's customer support.
 
 ```sh
-export VARIOMEDIA_API_TOKEN="sdfsdfsdfljlbjkljlkjsdfoiwjesdfsdfsdfljlbjkljlkjsdfoiwje"
+export VARIOMEDIA_API_TOKEN="<token>"
 ```
 
 Ok, let's issue a cert now:
@@ -415,9 +461,14 @@ The `VARIOMEDIA_API_TOKEN` will be saved in `~/.acme.sh/account.conf` and will b
 If you find any bugs, please report here: https://github.com/Neilpang/acme.sh/issues/2564
 
 
+<a name="dns_pleskxml"/>
+
 ## 92. Use Plesk XML API to automatically issue cert
 
-Before using the module, you must set your Plesk user name and password, and the address of your Plesk XML API (sometimes called a URI, URL or web link). The URI usually looks similar to this:
+Before using the module, you must set your Plesk username and password,
+and the address of your Plesk XML API (sometimes called a URI, URL or web link).
+
+The URI usually looks similar to this:
 
 ```
 https://address-of-my-plesk-server.net:8443/enterprise/control/agent.php
@@ -438,7 +489,11 @@ Ok, let's issue a cert now:
 
 The `pleskxml_uri`, `pleskxml_user` and `pleskxml_pass` will be saved in `~/.acme.sh/account.conf` and reused when needed.
 
-If you find any bugs, please report here: https://github.com/Neilpang/acme.sh/issues/2577
+If you find any bugs, please report here:
+https://github.com/Neilpang/acme.sh/issues/2577
+
+
+<a name="dns_pdnsmanager"/>
 
 ## 93. Use PDNS Manager API
 
@@ -447,9 +502,9 @@ If you find any bugs, please report here: https://github.com/Neilpang/acme.sh/is
 This script uses PDNS Manager API and its "[Update via GET request](https://pdnsmanager.org/documentation/api/)" method. So only single record update possible and no wildcards, for now.
 
 ```sh
-export PDNS_MANAGER_URL=https://mypdnsmanagerurl.nx
-export PDNS_MANAGER_RECORDID=<record id>
-export PDNS_MANAGER_PASSWORD=<record password>
+export PDNS_MANAGER_URL="https://mypdnsmanagerurl.nx"
+export PDNS_MANAGER_RECORDID="<record id>"
+export PDNS_MANAGER_PASSWORD="<record password>"
 ```
 
 * Add your domain to PDNS Manager.
@@ -458,15 +513,18 @@ export PDNS_MANAGER_PASSWORD=<record password>
 Then issue a new certificate:
 
 ```sh
-./acme.sh --issue -d example.com --dns dns_pdnsmanager
+./acme.sh --issue --dns dns_pdnsmanager -d example.com
 ```
 
+
+<a name="dns_misaka"/>
+
 ## 94. Use Misaka.io domain API
 
 Get your API token at https://console.misaka.io/settings
 
 ```sh
-export Misaka_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export Misaka_Key="<key>"
 ```
 
 To issue a cert:
@@ -474,6 +532,9 @@ To issue a cert:
 ./acme.sh --issue --dns dns_misaka -d example.com -d www.example.com
 ```
 
+
+<a name="dns_easydns"/>
+
 ## 95. Use easyDNS.net API to automatically issue a cert
 You need to sign up for API access [here](https://cp.easydns.com/manage/security/api/signup.php) or select 'User' -> 'Security' from the top menu and select 'signup' in the 'easyDNS REST API' section after logging in to your account.
 API Docs: https://sandbox.rest.easydns.net:3001/
@@ -493,9 +554,11 @@ Ok, let's issue a cert now:
 The `EASYDNS_Token` and `EASYDNS_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 If you find any bugs, please report here:
-
 https://github.com/acmesh-official/acme.sh/issues/2647
 
+
+<a name="dns_clouddns"/>
+
 ## 96. Use CloudDNS API to automatically issue a cert
 Docs: https://github.com/vshosting/clouddns
 
@@ -515,8 +578,11 @@ If you find any bugs, please report here:
 
 https://github.com/Neilpang/acme.sh/issues/2699
 
+
+<a name="dns_dynv6"/>
+
 ## 97. Use dynv6 API to automatically issue a cert
-This uses the [dynv6 SSH API](https://dynv6.com/docs/apis) to issue the certificate. You will need a ssh key to authenticate. You can specify your own key with `export KEY="path/to/keyfile"` or if no key is specified one will be created for you which you will have to add [here](https://dynv6.com/keys). In both cases the path to the keyfile will be saved for reuse. 
+This uses the [dynv6 SSH API](https://dynv6.com/docs/apis) to issue the certificate. You will need a ssh key to authenticate. You can specify your own key with `export KEY="path/to/keyfile"` or if no key is specified one will be created for you which you will have to add [here](https://dynv6.com/keys). In both cases the path to the keyfile will be saved for reuse.
 
 Alternatively you can use the [HTTP REST API](https://dynv6.github.io/api-spec/). For this you will need a HTTP Token, which you can generate from the [dynv6 website](https://dynv6.com/keys). Use it with `export DYNV6_TOKEN="value"`.
 
@@ -526,16 +592,20 @@ To issue a cert use:
 ```sh
 ./acme.sh --issue --dns dns_dynv6 -d www.example.dynv6.net
 ```
+
 If you find any bugs, please report here:  
 https://github.com/acmesh-official/acme.sh/issues/2702
 
+
+<a name="dns_kas"/>
+
 ## 98. Use All-Inkl.com domain API to automatically issue cert
 
 You need your login credentials for All-Inkl (https://kas.all-inkl.com).
 ```sh
-export KAS_Login=<ACCOUNTID> 
-export KAS_Authdata=<PLAINTEXTPASSWORD>
-export KAS_Authtype=plain
+export KAS_Login="<ACCOUNTID>" 
+export KAS_Authdata="<PLAINTEXTPASSWORD>"
+export KAS_Authtype="plain"
 ```
 Now you are able to issue a cert:
 ```sh
@@ -543,6 +613,9 @@ Now you are able to issue a cert:
 ```
 The `KAS_Login`, `KAS_Authtype` and `KAS_Authdata` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_constellix"/>
+
 ## 99. Use Constellix domain API
 
 Get your API credentials at https://manage.constellix.com/users
@@ -559,9 +632,12 @@ To issue a cert:
 
 The `CONSTELLIX_Key` and `CONSTELLIX_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_nm"/>
+
 ## 100. Use Namemaster domain API
 
-Get your API credentials at https://namemaster.de DNS/API 
+Get your API credentials at https://namemaster.de DNS/API
 
 ```sh
 export NM_user="XXX"
@@ -575,6 +651,9 @@ To issue a cert:
 
 The `NM_user` and `NM_sha256` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_hostingukraine"/>
+
 ## 101. Use HostingUkraine domain API
 
 How get your API credentials: https://api.adm.tools/osnovnie-polozheniya/dostup-k-api/
@@ -590,19 +669,22 @@ To issue a cert:
 ```sh
 ./acme.sh --issue --dns dns_hostingukraine -d yourdomain.com -d www.yourdomain.com
 ```
-To issue a wildcard cert: 
+To issue a wildcard cert:
 ```sh
 ./acme.sh --issue --dns dns_hostingukraine -d yourdomain.com -d '*.yourdomain.com' 
 ```
 
 The `HostingUkraine_Login` and `HostingUkraine_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_arvan"/>
+
 ## 102. Use ArvanCloud domain API
 
 Get your API token at https://npanel.arvancloud.com/profile/api-keys
 
 ```sh
-export Arvan_Token="fsdasdfsdfljlbjkljlkjsdfoiwje"
+export Arvan_Token="<token>"
 ```
 
 To issue a cert:
@@ -612,6 +694,9 @@ To issue a cert:
 
 The `Arvan_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_joker"/>
+
 ## 103. Use Joker.com domain API
 
 You must activate Dynamic DNS in Joker.com DNS configuration first. Username and password below refer to Dynamic DNS authentication, not your Joker.com login credentials. See https://joker.com/faq/content/11/427/en/what-is-dynamic-dns-dyndns.html.
@@ -633,23 +718,26 @@ To issue a cert:
 
 The `JOKER_USERNAME`  and `JOKER_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_1984hosting"/>
+
 ## 104. Use 1984Hosting domain API
 
-[1984Hosting](https://1984hosting.com/) 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 1984Hosting 
-website to read the HTML and posting updates as HTTP. The plugin needs to 
+[1984Hosting](https://1984hosting.com/) 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 1984Hosting
+website to read the HTML and posting updates as HTTP. The plugin needs to
 know your username and password for the 1984Hosting website.
 
 ```sh
-export One984HOSTING_Username=<your_username>
-export One984HOSTING_Password=<your_password>
+export One984HOSTING_Username="<your_username>"
+export One984HOSTING_Password="<your_password>"
 ```
 
-You need only provide this the first time you run the `acme.sh` client with 1984Hosting 
-validation and then again whenever you change your password at the 1984Hosting site. 
-The `acme.sh` 1984Hosting plugin does not store your username or password, 
-but rather saves an authentication token returned by 1984Hosting 
+You need only provide this the first time you run the `acme.sh` client with 1984Hosting
+validation and then again whenever you change your password at the 1984Hosting site.
+The `acme.sh` 1984Hosting plugin does not store your username or password,
+but rather saves an authentication token returned by 1984Hosting
 in `~/.acme.sh/account.conf` and reuses it when needed.
 
 Ok, let's issue a cert now:
@@ -660,13 +748,16 @@ Ok, let's issue a cert now:
 
 If you have any issues with 1984Hosting DNS API please report them [here](https://github.com/Neilpang/acme.sh/issues/2851).
 
+
+<a name="dns_aruba"/>
+
 ## 105. Use Aruba domain API
 
 Get your api token following instruction here at https://admin.arubabusiness.it/DashBoard/WebApiGuide.aspx
 ```sh
-export ARUBA_TK="sdfsdfsdfljlbjkljlkjsdfoiwje" #ARUBA API Token
-export ARUBA_AK="xxxxxxxxxxxxx" #ARUBA Username
-export ARUBA_AS="xxxxxxxxxxxxx" #ARUBA Password
+export ARUBA_TK="<API Token>"
+export ARUBA_AK="<Username>" 
+export ARUBA_AS="<Password>" 
 ```
 Ok, let's issue a cert now:
 ```sh
@@ -677,6 +768,8 @@ If you find any bugs, please report here:
 https://github.com/JTrotta/acme.sh/issues
 
 
+<a name="dns_transip"/>
+
 ## 106. Use TransIP domain API:
 
 First you need to login to your TransIP account to get your [private key](https://www.transip.nl/cp/account/api/).
@@ -690,9 +783,9 @@ Note 2: if the DNS fails with something like
 Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
 == Info: SSL certificate problem: unable to get local issuer certificate
 ```
-Than maybe the root CA of TransIP is NOT in your cacerts.
+Then maybe the root CA of TransIP is NOT in your cacerts.
 You can check this manually with
-```
+```sh
 curl -vvI https://api.transip.nl
 ```
 Currently, the root CA of TransIP is COMODO_RSA_Certification_Authority.crt
@@ -712,6 +805,9 @@ To issue a cert:
 ./acme.sh --issue --dns dns_transip --dnssleep 300 -d example.com -d www.example.com
 ```
 
+
+<a name="dns_df"/>
+
 ## 107. Use dyndnsfree.de API
 
 ```sh
@@ -726,10 +822,13 @@ To issue a cert:
 
 The `df_user` and `df_password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_njalla"/>
+
 ## 108. Use Njalla API
 
 ```sh
-export NJALLA_Token="XXX"
+export NJALLA_Token="<token>"
 ```
 
 To issue a cert:
@@ -740,12 +839,14 @@ To issue a cert:
 Please report any bugs here: https://github.com/acmesh-official/acme.sh/issues/2913
 
 
+<a name="dns_vercel"/>
+
 ## 109. Use Vercel API
 
 Obtain an account token from https://vercel.com/account/tokens.
 
 ```sh
-export VERCEL_TOKEN="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export VERCEL_TOKEN="<token>"
 ```
 
 To issue a cert:
@@ -754,12 +855,14 @@ To issue a cert:
 ```
 
 
+<a name="dns_hetzner"/>
+
 ## 110. Use Hetzner DNS API
 
 First you need to create/obtain API tokens on your [Hetzner DNS console](https://dns.hetzner.com/settings/api-token).
 
 ```sh
-export HETZNER_Token="somelongrandomstring"
+export HETZNER_Token="<token>"
 ```
 
 Ok, let's issue a cert now:
@@ -768,14 +871,17 @@ Ok, let's issue a cert now:
 ```
 
 The `HETZNER_Token` settings will be saved in `[acme.sh-config-home-path]/account.conf`
- and will be reused when needed.
-The domain(s) zone_id(s) will be saved in `CERT_HOME/[domain]/[domain].conf` 
-in order to avoid multiple `get_zone_id` requests two months later. 
+and will be reused when needed.
+The domain(s) zone_id(s) will be saved in `CERT_HOME/[domain]/[domain].conf`
+in order to avoid multiple `get_zone_id` requests two months later.
 
 > If you're not already using the new "gases" name servers (hydrogen, oxygen and helium)
 > don't forget to change the domain's whois ns section to them and wait about 24-48 Hours.
 > See [Hetzner wiki](https://docs.hetzner.com/dns-console/dns/general/what-has-changed).
 
+
+<a name="dns_kappernet"/>
+
 ## 111. Use kapper.net DNS API
 Contact kapper.net support via support@kapper.net to get your kapper.net DNS Panel API Key and Secret.
 
@@ -795,7 +901,7 @@ or for a wildcertificate
 ./acme.sh --issue --dns dns_kappernet -d <example.com> -d *.<example.com> 
 
 ```
-Please replace "<example.com>" with the name of the domain you wish to create a certificate for.
+Please replace `<example.com>` with the name of the domain you wish to create a certificate for.
 
 After the test you can replace your kapper.net DNS Panel API Key and Secret, it is stored in ~/.acme.sh/account.conf.
 
@@ -804,6 +910,9 @@ For repeated calls use
 ./acme.sh --issue --dns dns_kappernet -d <example.com>
 ```
 
+
+<a name="dns_wedos"/>
+
 ## 112. Use Wedos API
 
 First create your WAPI password and add your IP address to access list at customer portal. For more info visit, [https://kb.wedos.com/en/kategorie/wapi-api-interface/](https://kb.wedos.com/en/kategorie/wapi-api-interface/)
@@ -824,6 +933,9 @@ Issue your certs:
 
 WEDOS_User and WEDOS_Hash will be stored in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_shellrent"/>
+
 ## 113. Use Shellrent API
 
 Shellrent API offers one method to automatically issue certs.
@@ -833,14 +945,14 @@ In order to use the token, you need to authorize your IP to have access to it.
 More Info on https://api.shellrent.com and https://guide.shellrent.com
 ```sh
 export SH_Username="usrXXXX"
-export SH_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export SH_Token="<token>"
 ```
 
 Alternatively, if the certificate only covers a single zone, you can speed up the process by specify the SH_Domain_ID directly:
 
 ```sh
 export SH_Username="usrXXXX"
-export SH_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
+export SH_Token="<token>"
 export SH_Domain_ID="xxxxxxxxxxxxx"
 ```
 Let's issue a cert now:
@@ -850,6 +962,9 @@ Let's issue a cert now:
 ```
 The SH_Username and SH_Token and SH_Domain_ID will be saved in ~/.acme.sh/account.conf and will be reused when needed.
 
+
+<a name="dns_openstack"/>
+
 ## 114. Use OpenStack domain API
 
 This provider supports [OpenStack Designate](https://docs.openstack.org/designate)
@@ -871,12 +986,12 @@ You will most likely want to source your OpenStack RC file to set your environme
 ```
 or manually like:
 ```sh
-export OS_AUTH_URL=https://keystone.example.com:5000/
-export OS_USERNAME=<username>
-export OS_PASSWORD=<password>
-export OS_PROJECT_NAME=<project name>
-export OS_PROJECT_DOMAIN_NAME=Default
-export OS_USER_DOMAIN_NAME=Default
+export OS_AUTH_URL="https://keystone.example.com:5000/"
+export OS_USERNAME="<username>"
+export OS_PASSWORD="<password>"
+export OS_PROJECT_NAME="<project name>"
+export OS_PROJECT_DOMAIN_NAME="Default"
+export OS_USER_DOMAIN_NAME="Default"
 ```
 
 To issue a cert:
@@ -886,6 +1001,9 @@ To issue a cert:
 
 Your OpenStack credentials will be saved to `~/.acme.sh/account.conf` and reused on renewal.
 
+
+<a name="dns_netlify"/>
+
 ## 115. Use Netlify API
 
 1. Generate a Personal Access Token at https://app.netlify.com/user/applications
@@ -893,7 +1011,7 @@ Your OpenStack credentials will be saved to `~/.acme.sh/account.conf` and reused
 2. Set your token for use with
 
 ```sh
-export NETLIFY_ACCESS_TOKEN='arstdhneioqwfpgjluyzxcvbkm'
+export NETLIFY_ACCESS_TOKEN='<token>'
 ```
 
 3.  Issue a cert with:
@@ -904,6 +1022,9 @@ export NETLIFY_ACCESS_TOKEN='arstdhneioqwfpgjluyzxcvbkm'
 
 [Report a Netlify-related Bug](https://github.com/acmesh-official/acme.sh/issues/3088)
 
+
+<a name="dns_edgedns"/>
+
 ## 116. Use Akamai Edge DNS API
 
 This provider supports the [Akamai Edge DNS](https://developer.akamai.com/api/cloud_security/edge_dns_zone_management/v2.html) API for creating DNS records.
@@ -914,10 +1035,10 @@ This provider requires Akamai Open Edgegrid Credentials with EdgeDNS API access
 
 The Akamai Open Edgegrid credentials must be specified as environment variables as follows:
 ```sh
-export AKAMAI_CLIENT_TOKEN=<akamai edgegrid client token>
-export AKAMAI_ACCESS_TOKEN=<akamai edgegrid access token>
-export AKAMAI_CLIENT_SECRET=<akamai edgegrid client secret>
-export AKAMAI_HOST=<akamai edgegrid api host>
+export AKAMAI_CLIENT_TOKEN="<akamai edgegrid client token>"
+export AKAMAI_ACCESS_TOKEN="<akamai edgegrid access token>"
+export AKAMAI_CLIENT_SECRET="<akamai edgegrid client secret>"
+export AKAMAI_HOST="<akamai edgegrid api host>"
 ```
 
 To issue a cert:
@@ -927,13 +1048,22 @@ To issue a cert:
 
 Your Akamai Edgegrid credentials will be saved to `~/.acme.sh/account.conf` and reused on renewal.
 
-## 117. Use WEDOS DNS API
-WEDOS DNS provider comes from Czech Republic. DNS API implementation for WEDOS require your WEDOS's account to allow WAPI interface. You have to login to WEDOS administration, in setting allow WAPI interface (in days when this manual were written it was for free completelly). Configure WAPI interface to XML interface and register the IP addresses (IPv4 and IPv6) of the server where you plan to use acme.sh. That is from the manual side.
 
-By doing this setting you should have WEDOS web account username and configured WAPI password. This must be configured to your acme.sh account in the first execution of acme.sh script. To save it to `~/.acme.sh/account.conf` (and for subsequent acme.sh executions) just execute following before first execution of acme.sh script.
+<a name="dns_wedos"/>
+
+## 117. Use WEDOS DNS API
+WEDOS DNS provider comes from Czech Republic.
+DNS API implementation for WEDOS require your WEDOS's account to allow WAPI interface.
+You have to login to WEDOS administration, in setting allow WAPI interface (in days when this manual were written it was for free completelly).
+Configure WAPI interface to XML interface and register the IP addresses (IPv4 and IPv6) of the server where you plan to use acme.sh.
+That is from the manual side.
+
+By doing this setting you should have WEDOS web account username and configured WAPI password.
+This must be configured to your acme.sh account in the first execution of acme.sh script.
+To save it to `~/.acme.sh/account.conf` (and for subsequent acme.sh executions) just execute following before first execution of acme.sh script.
 ```sh
-export WEDOS_Username=<your user name to login to wedos web account>
-export WEDOS_Wapipass=<your WAPI passwords you setup using wedos web pages>
+export WEDOS_Username="<your user name to login to wedos web account>"
+export WEDOS_Wapipass="<your WAPI passwords you setup using wedos web pages>"
 ```
 
 Then you can issue a certificates:
@@ -941,15 +1071,18 @@ Then you can issue a certificates:
 ./acme.sh --issue --dns dns_wedos -d "*.example.com" -d "examle.com"
 ```
 
-If you face any bug, please use this [page](https://github.com/acmesh-official/acme.sh/issues/3166) to report it. But before reporting run the acme.sh with `--debug 2` switch and append full acme.sh output to the issue report. 
+If you face any bug, please use this [page](https://github.com/acmesh-official/acme.sh/issues/3166) to report it.
 
-Enjoy it.
+But before reporting run the acme.sh with `--debug 2` switch and append full acme.sh output to the issue report.
+
+
+<a name="dns_websupport"/>
 
 ## 118. Use Websupport DNS API
 Obtain an api key and secret from https://admin.websupport.sk/en/auth/apiKey
 ```sh
-export WS_ApiKey="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
-export WS_ApiSecret="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+export WS_ApiKey="<key>"
+export WS_ApiSecret="<secret>"
 ```
 
 To issue a cert:
@@ -959,6 +1092,9 @@ To issue a cert:
 
 Report any issues to https://github.com/akulumbeg/acme.sh/issues
 
+
+<a name="dns_infomaniak"/>
+
 ## 119. Use infomaniak.com API
 
 Infomaniak hosts a large number of domains and other hosted services.
@@ -971,7 +1107,10 @@ export INFOMANIAK_API_TOKEN=xxx
 ./acme.sh --issue --dns dns_infomaniak -d example.com -d www.example.com
 ```
 
-Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3188
+Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3188)
+
+
+<a name="dns_bookmyname"/>
 
 ## 120. Use bookmyname.com API
 
@@ -980,12 +1119,15 @@ Bookmyname hosts domains and has a small API.
 Export your login/pass as an environment variable:
 
 ```sh
-export BOOKMYNAME_USERNAME=xxx
-export BOOKMYNAME_PASSWORD=yyy
+export BOOKMYNAME_USERNAME="xxx"
+export BOOKMYNAME_PASSWORD="yyy"
 ./acme.sh --issue --dns dns_bookmyname --dnssleep 600 -d example.com -d www.example.com
 ```
 
-Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3209
+Please report any issue to [here](https://github.com/acmesh-official/acme.sh/issues/3209)
+
+
+<a name="dns_anx"/>
 
 ## 121. Use anexia.com CloudDNS API
 
@@ -994,10 +1136,14 @@ For DNS records managed via https://engine.anexia-it.com/clouddns
 Export your token as an environment variable:
 
 ```sh
-export ANX_Token='XXXXXXXXXXXXXXXXXXX'
+export ANX_Token='<token>'
 ./acme.sh --issue --dns dns_anx -d example.com -d www.example.com
 ```
-Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3238
+
+Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3238)
+
+
+<a name="dns_synology_dsm"/>
 
 ## 122. Use Synology DSM Synology DNS Server API
 Note that in order the script to be working properly acme.sh should be installed on Synology itself.
@@ -1007,22 +1153,25 @@ To issue a cert:
 ./acme.sh --issue --dns dns_synology_dsm -d example.com -d www.example.com
 ```
 To issue a wildcard cert:
-```
+```sh
 ./acme.sh --issue --dns dns_synology_dsm -d example.com -d *.example.com
 ```
 You can find more details [here](https://github.com/arabezar/acme.sh/wiki)
 
 Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3248)
 
+
+<a name="dns_huaweicloud"/>
+
 ## 123. Use HuaweiCloud API
 Export your credentials as an environment variable:
 
-About "DomainName" parameters see: https://support.huaweicloud.com/api-iam/iam_01_0006.html
+About `DomainName` parameters see: https://support.huaweicloud.com/api-iam/iam_01_0006.html
 
 ```sh
-export HUAWEICLOUD_Username=<Your Username> # IAM Username
-export HUAWEICLOUD_Password=<Your Password>
-export HUAWEICLOUD_DomainName=<Your DomainName>
+export HUAWEICLOUD_Username="<Your IAM Username>"
+export HUAWEICLOUD_Password="<Your Password>"
+export HUAWEICLOUD_DomainName="<Your DomainName>"
 ```
 
 To issue a cert:
@@ -1034,12 +1183,15 @@ To issue a wildcard cert:
 ./acme.sh --issue --dns dns_huaweicloud -d example.com -d *.example.com
 ```
 
+
+<a name="dns_simply"/>
+
 ## 124. Use Simply.com API
 Export your credentials, you will find your API key by logging in to your Simply.com account [here](https://www.simply.com/controlpanel/account/):
 
 ```sh
-export SIMPLY_AccountName=<Your accountname>
-export SIMPLY_ApiKey=<Your API-key>
+export SIMPLY_AccountName="<Your accountname>"
+export SIMPLY_ApiKey="<Your API-key>"
 ```
 
 To issue a cert:
@@ -1051,12 +1203,15 @@ To issue a wildcard cert:
 ./acme.sh --issue --dns dns_simply -d example.com -d *.example.com
 ```
 
+
+<a name="dns_world4you"/>
+
 ## 125. Use World4You API
 Export your credentials as an environment variable:
 
 ```sh
-export WORLD4YOU_USERNAME=<customer-id>
-export WORLD4YOU_PASSWORD=<password>
+export WORLD4YOU_USERNAME="<customer-id>"
+export WORLD4YOU_PASSWORD="<password>"
 ```
 
 To issue a cert:
@@ -1068,6 +1223,9 @@ To issue a wildcard cert:
 ./acme.sh --issue --dns dns_world4you -d example.com -d *.example.com
 ```
 
+
+<a name="dns_scaleway"/>
+
 ## 126. Use Scaleway API
 
 First, you'll need to retrieve your [Api Key](https://www.scaleway.com/en/docs/generate-api-keys/)
@@ -1084,6 +1242,9 @@ To issue a cert run:
 
 Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3295)
 
+
+<a name="dns_ls"/>
+
 ## 127 First you need to login to your LS account to get your API Key.
 
 ```sh
@@ -1095,6 +1256,9 @@ Ok, let's issue a cert now:
 ./acme.sh --issue --dns dns_ls -d example.com -d www.example.com
 ```
 
+
+<a name="dns_rackcorp"/>
+
 ## 128. Use RackCorp API
 Export your credentials as an environment variable:
 ```sh
@@ -1110,6 +1274,9 @@ To issue a wildcard cert:
 ./acme.sh --issue --dns dns_rackcorp -d example.com -d *.example.com
 ```
 
+
+<a name="dns_ionos"/>
+
 ## 129. Using the IONOS domain API
 
 Read [Getting Started](https://developer.hosting.ionos.de/docs/getstarted) to learn how to create an API key.
@@ -1130,6 +1297,9 @@ To issue a wildcard certificate, execute:
 ./acme.sh --issue --dns dns_ionos -d example.com -d *.example.com
 ```
 
+
+<a name="dns_porkbun"/>
+
 ## 130. Using the Porkbun API
 
 Read [Getting Started](https://porkbun.com/api/json/v3/documentation) to learn how to create an API key.
@@ -1150,6 +1320,9 @@ To issue a wildcard certificate, execute:
 ./acme.sh --issue --dns dns_porkbun -d example.com -d *.example.com
 ```
 
+
+<a name="dns_aurora"/>
+
 ## 131. Using the Aurora API
 
 [PCextreme B.V.](https://www.pcextreme.nl/) is a Dutch cloud provider offering cloud services under the family name Aurora. Head over to [DNS & Health Checks > Users](https://cp.pcextreme.nl/auroradns/users) to get your API credentials.
@@ -1167,6 +1340,9 @@ To issue a certificate, execute:
 
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3459
 
+
+<a name="dns_azion"/>
+
 ## 132. Using the Azion DNS API
 
 [Azion](https://www.azion.com/) is a Edge Computing Platform to build modern applications at edge. This API reflects the [Intelligent DNS](https://www.azion.com/en/documentation/products/intelligent-dns/) product. Read this [documentation](https://www.azion.com/en/documentation/products/api/v3/) to create an username/password and permissions to use this plugin.
@@ -1184,10 +1360,16 @@ To issue a certificate, execute:
 
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3555
 
+
+<a name="dns_oci"/>
+
 ## 133. Using Oracle Cloud Infrastructure DNS
 
 See: <https://github.com/acmesh-official/acme.sh/wiki/Using-Oracle-Cloud-Infrastructure-DNS>
 
+
+<a name="dns_hostline"/>
+
 ## 134. Utilisation de l'API DNS Hostline Hébergement VPS
 
 Créer un token API sur votre compte [Hostline Hébergement VPS](https://www.hostline.fr).
@@ -1211,6 +1393,9 @@ Les variables `HOSTLINE_Token`, `HOSTLINE_Url` (optionnel) et `HOSTLINE_Ttl` (op
 Si vous rencontrez un problème sur l'API Hostline Hébergement VPS, merci de rapporter votre problème sur le lien suivant : [https://github.com/acmesh-official/acme.sh/issues/3675](https://github.com/acmesh-official/acme.sh/issues/3675)
 
 
+
+<a name="dns_veesp"/>
+
 ## 135. Use Veesp domain API
 
 [Veesp](https://veesp.com/) offers HTTP REST [API](https://secure.veesp.com/userapi#dns-82) to manage vital details of account and services like DNS. Your standard login credentials is needed:
@@ -1227,7 +1412,11 @@ To issue a cert:
 
 The `VEESP_User` and `VEESP_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-Please report any issue to [https://github.com/acmesh-official/acme.sh/issues/3712](https://github.com/acmesh-official/acme.sh/issues/3712)
+Please report any issue here:
+https://github.com/acmesh-official/acme.sh/issues/3712
+
+
+<a name="dns_cpanel"/>
 
 ## 136. Use cPanel DNS systems
 
@@ -1235,16 +1424,16 @@ First you need to log into the cPanel interface and generate an API key for your
 Then set your username, api token and hostname:
 
 ```sh
-export cPanel_Username=username
-export cPanel_Apitoken=apitoken
-export cPanel_Hostname=https://hostname:port
+export cPanel_Username="username"
+export cPanel_Apitoken="apitoken"
+export cPanel_Hostname="https://hostname:port"
 ```
 example
 
 ```sh
-export cPanel_Username=myadminuseratnordicway
-export cPanel_Apitoken=CXJ8HRXFNS363RQ71Z51TKM9KTHRFZVE
-export cPanel_Hostname=https://cp04.nordicway.dk:2083
+export cPanel_Username="myadminuseratnordicway"
+export cPanel_Apitoken="CXJ8HRXFNS363RQ71Z51TKM9KTHRFZVE"
+export cPanel_Hostname="https://cp04.nordicway.dk:2083"
 ```
 
 Ok, let's issue a cert now:
@@ -1256,18 +1445,22 @@ Ok, let's issue a cert now:
 
 The `cPanel_Username`, `cPanel_Apitoken` and `cPanel_Hostname` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-Please report any issue to [https://github.com/acmesh-official/acme.sh/issues/3732](https://github.com/acmesh-official/acme.sh/issues/3732)
+Please report any issue here:
+https://github.com/acmesh-official/acme.sh/issues/3732
+
+
+<a name="dns_ispman"/>
 
 ## 137. Use ISPMan domain API
 
-!!! IMPORTANT: Make sure the verson of ISPMan supports TXT records !!!
+!!! IMPORTANT: Make sure the version of ISPMan supports TXT records !!!
 
 The `dns_ispman.sh` api Adds & Deletes domain TXT records by authenticating into the [ISPMan](http://ispman.sourceforge.net/) Customer Control Panel and executing related HTTP POST & GET requests.
 
 The `dns_ispman.sh` api requires your `<domain>` and `<passwd>` for authentication:
 ```sh
-export ISPMan_Username=<domain>
-export ISPMan_Password=<passwd>
+export ISPMan_Username="<domain>"
+export ISPMan_Password="<passwd>"
 ```
 
 The `ISPMan_Username` and `ISPMan_Password` will be saved in `$LE_WORKING_DIR/account.conf` and will be reused for certificate renewals.
@@ -1278,7 +1471,11 @@ Ok, let's issue a cert:
 ./acme.sh --issue --dns dns_ispman -d example.com -d *.example.com
 ```
 
-Please report bugs to [https://github.com/acmesh-official/acme.sh/issues/3751](https://github.com/acmesh-official/acme.sh/issues/3751)
+Please report bugs here:
+https://github.com/acmesh-official/acme.sh/issues/3751
+
+
+<a name="dns_dnshome"/>
 
 ## 138. Use dnsHome.de DNS API
 
@@ -1294,7 +1491,11 @@ Ok, let's issue a cert now:
 
 The `DNSHOME_Subdomain` and `DNSHOME_SubdomainPassword` will be saved in the domain conf and will be reused when needed.
 
-Please report any issue to [https://github.com/acmesh-official/acme.sh/issues/3819](https://github.com/acmesh-official/acme.sh/issues/3819)
+Please report any issue here:
+https://github.com/acmesh-official/acme.sh/issues/3819
+
+
+<a name="dns_mythic_beasts"/>
 
 ## 139. Use mythic-beasts.com DNS API
 
@@ -1315,9 +1516,12 @@ The credentials will be saved in `~/.acme.sh/account.conf` and will be reused wh
 Please report any issue to [https://github.com/acmesh-official/acme.sh/issues/3848](https://github.com/acmesh-official/acme.sh/issues/3848)
 
 
+
+<a name="dns_sdns"/>
+
 ## 140. Use s-dns.de API
 
-First generate your dns zone key. Open your existing nameserver entry, click on [Passwort für dynamic DNS generieren] and save your zone. This generates a new key for your zone. 
+First generate your dns zone key. Open your existing nameserver entry, click on [Passwort für dynamic DNS generieren] and save your zone. This generates a new key for your zone.
 
 ```sh
 export SDNS_ZONE_KEY="Key"
@@ -1334,6 +1538,9 @@ S-dns nameservers use anycast. It is therefore possible that the server next to
 ./acme.sh --issue --dns dns_sdns --domain example.com --dnssleep 240
 ```
 
+
+<a name="dns_udr"/>
+
 ## 141. Using the united-domains reselling DNS API
 
 Create an account at [ud reselling](https://www.ud-reselling.com/).
@@ -1357,6 +1564,9 @@ To issue a wildcard certificate, execute:
 
 The `UDR_USER` and `UDR_PASS` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_curanet"/>
+
 ## 142. Using the curanet DNS API
 
 Login to your curanet account, create a new API Application, and use client_id and secret as shown below
@@ -1378,6 +1588,9 @@ To issue a wildcard certificate, execute:
 
 The `CURANET_AUTHCLIENTID` and `CURANET_AUTHSECRET` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_artfiles"/>
+
 ## 143. Use ArtFiles.de DNS API
 
 First, verify that API access is already enabled:
@@ -1402,7 +1615,11 @@ To issue a wildcard certificate, execute:
 ./acme.sh --issue --dns dns_artfiles -d yourDomain.tld -d *.yourDomain.tld
 ```
 
-Please report any issue at [Eagle3386/acme.sh/issues](https://github.com/Eagle3386/acme.sh/issues).
+Please report any issue here:
+https://github.com/Eagle3386/acme.sh/issues
+
+
+<a name="dns_geoscaling"/>
 
 ## 144. Use Geoscaling.com DNS2
 
@@ -1426,7 +1643,11 @@ To issue a wildcard certificate, execute:
 ```
 
 The `GEOSCALING_Username` and `GEOSCALING_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
-Report bugs [at this issue](https://github.com/acmesh-official/acme.sh/issues/3969).
+Report bugs here:
+https://github.com/acmesh-official/acme.sh/issues/3969
+
+
+<a name="dns_fornex"/>
 
 ## 145. Use fornex.com API
 
@@ -1445,29 +1666,36 @@ To issue a wildcard certificate, execute:
 ./acme.sh --issue --dns dns_fornex -d example.com -d '*.example.com'
 ```
 
+
+<a name="dns_dnsservices"/>
+
 ## 146. Use DNS.Services API
 
 Use your credentials
-
-    export DnsServices_Username=user@example.com
-    export DnsServices_Password=YouPassword
-
+```sh
+export DnsServices_Username="user@example.com"
+export DnsServices_Password="YouPassword"
+```
 
 To issue a cert, run command:
-
-    ./acme.sh --issue --dns dns_dnsservices -d example.com
-
+```sh
+./acme.sh --issue --dns dns_dnsservices -d example.com
+```
 
 To issue a wildcard certificate, run command:
+```sh
+./acme.sh --issue --dns dns_dnsservices -d example.com -d '*.example.com'
+```
 
-    ./acme.sh --issue --dns dns_dnsservices -d example.com -d '*.example.com'
+
+<a name="dns_nodion"/>
 
 ## 147. Use Nodion DNS API
 
 You are able to create a free account on [app.nodion.com](https://app.nodion.com) and add an API key used by acme.sh by visiting the [settings page](https://app.nodion.com/user/security). Please take this token and set it as env variable.
 
 ```sh
-export NODION_API_KEY="Token"
+export NODION_API_KEY="<Token>"
 ```
 To issue a certificate, execute:
 
@@ -1481,22 +1709,29 @@ To issue a wildcard certificate, execute:
 acme.sh --issue --dns dns_nodion -d *.example.com
 ```
 
+
+<a name="dns_la"/>
+
 ## 148. Use dns.la API
 
 Use your credentials
-
-    export LA_Id="appid"
-    export LA_Key="apikey"
-
+```sh
+export LA_Id="appid"
+export LA_Key="apikey"
+```
 
 To issue a cert, run command:
-
-    ./acme.sh --issue --dns dns_la -d example.com
-
+```sh
+./acme.sh --issue --dns dns_la -d example.com
+```
 
 To issue a wildcard certificate, run command:
+```sh
+./acme.sh --issue --dns dns_la -d example.com -d *.example.com
+```
 
-    ./acme.sh --issue --dns dns_la -d example.com -d *.example.com
+
+<a name="dns_yc"/>
 
 ## 149. Use Yandex Cloud DNS API
 
@@ -1517,7 +1752,7 @@ Optional parameters:
 export YC_Zone_ID="DNS Zone ID"
 ```
 
-Now you cann issue a cert:
+Now you can issue a cert:
 
 ```sh
 ./acme.sh --issue --dns dns_yc -d example.com -d www.example.com
@@ -1525,6 +1760,9 @@ Now you cann issue a cert:
 
 Both, `YC_Folder_ID`, `YC_SA_ID`, `YC_SA_Key_ID`, `YC_SA_Key_File_PEM_b64` or `YC_SA_Key_File_Path` and `YC_Zone_ID` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+
+<a name="dns_bunny"/>
+
 ## 150. Use Bunny DNS API to automatically issue cert
 
 Find your API key at https://panel.bunny.net/account
@@ -1543,19 +1781,22 @@ The `BUNNY_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reuse
 
 If you find any bugs with the Bunny DNS API integration, please report them here: https://github.com/Neilpang/acme.sh/issues/4296
 
+
+<a name="dns_selfhost"/>
+
 ## 151. Use Selfhost DNS API
 
 - create a new TXT record for a subdomainname with the needed prefix e.g. "_acme-challenge.example.com" (default) or "alias.example.com" (dns alias mode)
-  - for wildcard subdomains add a second TXT record for the identical subdomainname
+    - for wildcard subdomains add a second TXT record for the identical subdomainname
 - edit the TXT record and note the ID in (...) behind the subdomainname
 - export each subdomainname (including the prefix) and the corresponding record IDs in SELFHOSTDNS_MAP like "subdomainname:RID1:RID2"
-  - at least one RID must be set, up to two are supported for wildcard subdomains
-  - each entry must be seperated by a space
+    - at least one RID must be set, up to two are supported for wildcard subdomains
+    - each entry must be seperated by a space
 - export username and password in SELFHOSTDNS_USERNAME and SELFHOSTDNS_PASSWORD
 
 _Note: For `username` you have to use your account / customer number. You can find them in any invoice or on the right top of the selfhost dashboard._
 
-```
+```sh
 export SELFHOSTDNS_USERNAME="myname"
 export SELFHOSTDNS_PASSWORD="mypass"
 export SELFHOSTDNS_MAP="_acme-challenge.example.com:12345:98765 alias.example.com:11111"
@@ -1563,6 +1804,9 @@ export SELFHOSTDNS_MAP="_acme-challenge.example.com:12345:98765 alias.example.co
 acme.sh --issue -d example.com --dns dns_selfhost
 ```
 
+
+<a name="dns_rage4"/>
+
 ## 152. Use rage4 DNS API
 
 Use your credentials
@@ -1584,6 +1828,9 @@ To issue a wildcard certificate, run command:
 ./acme.sh --issue --dns dns_rage4 -d example.com -d *.example.com
 ```
 
+
+<a name="dns_gcore"/>
+
 ## 153. Use GCore DNS API
 
 Login to your [GCore](https://accounts.gcore.com/profile/api-tokens) account and create an API Key.
@@ -1604,6 +1851,9 @@ To issue a wildcard certificate, run command:
 ./acme.sh --issue --dns dns_gcore -d example.com -d \*.example.com
 ```
 
+
+<a name="dns_dynadot"/>
+
 ## 154. Use dynadot DNS API
 PENDING Pull Request: https://github.com/acmesh-official/acme.sh/pull/4510
 
@@ -1627,6 +1877,9 @@ DYNADOTAPI_RETRY_SLEEP=30
 * `DYNADOTAPI_API_RETRIES` number of times to attempt a DYNADOT api call.
 * `DYNADOTAPI_RETRY_SLEEP` sleep time between DYNADOT api calls (only applied if a call fails and DYNADOTAPI_API_RETRIES is set great than 1)
 
+
+<a name="dns_ipv64"/>
+
 ## 155. Use IPv64 DNS API
 
 Login to your [IPV64](https://ipv64.net/account.php?login) Account and copy your API Key.
@@ -1647,12 +1900,15 @@ To issue a wildcard certificate, run command:
 ./acme.sh --issue --dns dns_ipv64 -d example.com -d \*.example.com
 ```
 
+
+<a name="dns_nanelo"/>
+
 ## 156. Use Nanelo DNS API
 
 Login to your [Nanelo](https://nanelo.com) Account, navigate to Settings > API Keys and generate a new API Key. Copy it and set it like the following:
 
 ```sh
-export NANELO_TOKEN="your_nanelo_api_key"
+export NANELO_TOKEN="<your_nanelo_api_key>"
 ```
 
 To issue a cert, run the following command:
@@ -1666,14 +1922,18 @@ To issue a wildcard certificate, run the following command:
 ```sh
 ./acme.sh --issue --dns dns_nanelo -d example.com -d *.example.com
 ```
-Please report any bugs/issues regarding the Nanelo DNS Integration [here](https://github.com/acmesh-official/acme.sh/issues/4519).
+Please report any bugs/issues regarding the Nanelo DNS Integration here:
+https://github.com/acmesh-official/acme.sh/issues/4519
+
+
+<a name="dns_googledomains"/>
 
 ## 157. Use Google Domains DNS API
 
 Visit https://domains.google.com/registrar/ and click "Manage" on the domain. Then, in the Security settings, generate an access token for the ACME DNS API. Save this access token as it is only displayed once.
 
 ```sh
-export GOOGLEDOMAINS_ACCESS_TOKEN="generated-access-token"
+export GOOGLEDOMAINS_ACCESS_TOKEN="<generated-access-token>"
 ```
 
 To issue a cert, run the following:
@@ -1687,8 +1947,10 @@ The script tries to infer the zone registered with Google Domains by matching th
 export GOOGLEDOMAINS_ZONE="google-domains-zone"
 ```
 
-# ##################
-# Use custom API
+
+<a name="dns_myapi"/>
+
+## Use custom API
 
 If your API is not supported yet, you can write your own DNS API.
 
@@ -1704,14 +1966,15 @@ Let's assume you want to name it 'myapi':
 
 For more details, please check our sample script: [dns_myapi.sh](https://github.com/Neilpang/acme.sh/blob/master/dnsapi/dns_myapi.sh)
 
-See:  [DNS API Dev Guide](https://github.com/Neilpang/acme.sh/wiki/DNS-API-Dev-Guide)
+See: [DNS API Dev Guide](https://github.com/Neilpang/acme.sh/wiki/DNS-API-Dev-Guide)
 
 
+<a name="dns_lexicon"/>
+
+## Use lexicon DNS API
+
+[How to use lexicon DNS API](https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-DNS-API)
 
 -----------------------------------
 
 **More APIs coming soon...**
-
-# Use lexicon DNS API
-
-[How to use lexicon DNS API](https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-DNS-API)