diff --git a/deploy-monitoring-services.md b/deploy-monitoring-services.md
index b124889bb8cd7..f31b7921ebebd 100644
--- a/deploy-monitoring-services.md
+++ b/deploy-monitoring-services.md
@@ -28,8 +28,8 @@ Assume that the TiDB cluster topology is as follows:
 ```bash
 # Downloads the package.
 wget https://github.com/prometheus/prometheus/releases/download/v2.49.1/prometheus-2.49.1.linux-amd64.tar.gz
-wget https://download.pingcap.org/node_exporter-v1.3.1-linux-amd64.tar.gz
-wget https://download.pingcap.org/grafana-7.5.17.linux-amd64.tar.gz
+wget https://download.pingcap.com/node_exporter-v1.3.1-linux-amd64.tar.gz
+wget https://download.pingcap.com/grafana-7.5.17.linux-amd64.tar.gz
 ```
 
 {{< copyable "shell-regular" >}}
diff --git a/dm/dm-faq.md b/dm/dm-faq.md
index 5ee968c2986e6..97156b0f6cd24 100644
--- a/dm/dm-faq.md
+++ b/dm/dm-faq.md
@@ -243,7 +243,7 @@ This is a known bug of TiUP, which is fixed in TiUP v1.3.2. The following are tw
     2. Scale in and then scale out Grafana nodes in the cluster to restart the Grafana service.
 - Solution two:
     1. Back up the `deploy/grafana-$port/bin/public` folder.
-    2. Download the [TiUP DM offline package](https://download.pingcap.org/tidb-dm-v2.0.1-linux-amd64.tar.gz) and unpack it.
+    2. Download the [TiUP DM offline package](https://download.pingcap.com/tidb-dm-v2.0.1-linux-amd64.tar.gz) and unpack it.
     3. Unpack the `grafana-v4.0.3-**.tar.gz` in the offline package.
     4. Replace the folder `deploy/grafana-$port/bin/public` with the `public` folder in `grafana-v4.0.3-**.tar.gz`.
     5. Execute `tiup dm restart $cluster_name -R grafana` to restart the Grafana service.
diff --git a/dm/quick-start-create-task.md b/dm/quick-start-create-task.md
index e26a8d2987642..9f8457ee7bdbf 100644
--- a/dm/quick-start-create-task.md
+++ b/dm/quick-start-create-task.md
@@ -74,7 +74,7 @@ To run a TiDB server, use the following command:
 {{< copyable "shell-regular" >}}
 
 ```bash
-wget https://download.pingcap.org/tidb-community-server-v8.5.0-linux-amd64.tar.gz
+wget https://download.pingcap.com/tidb-community-server-v8.5.0-linux-amd64.tar.gz
 tar -xzvf tidb-latest-linux-amd64.tar.gz
 mv tidb-latest-linux-amd64/bin/tidb-server ./
 ./tidb-server
diff --git a/download-ecosystem-tools.md b/download-ecosystem-tools.md
index c577e81004c48..940ec7f33528b 100644
--- a/download-ecosystem-tools.md
+++ b/download-ecosystem-tools.md
@@ -25,14 +25,14 @@ TiDB Toolkit contains frequently used TiDB tools, such as data export tool Dumpl
 You can download TiDB Toolkit from the following link:
 
 ```
-https://download.pingcap.org/tidb-community-toolkit-{version}-linux-{arch}.tar.gz
+https://download.pingcap.com/tidb-community-toolkit-{version}-linux-{arch}.tar.gz
 ```
 
-`{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v8.5.0-linux-amd64.tar.gz`.
+`{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v8.5.0-linux-amd64.tar.gz`.
 
 > **Note:**
 >
-> If you need to download the [PD Control](/pd-control.md) tool `pd-ctl`, download the TiDB installation package separately from `https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz`.
+> If you need to download the [PD Control](/pd-control.md) tool `pd-ctl`, download the TiDB installation package separately from `https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz`.
 
 ## TiDB Toolkit description
 
diff --git a/pd-control.md b/pd-control.md
index 9efef28daedb7..960fa0da2293d 100644
--- a/pd-control.md
+++ b/pd-control.md
@@ -24,12 +24,12 @@ To obtain `pd-ctl` of the latest version, download the TiDB server installation
 
 | Installation package                                                                    | OS | Architecture | SHA256 checksum                                                    |
 | :------------------------------------------------------------------------ | :------- | :---- | :--------------------------------------------------------------- |
-| `https://download.pingcap.org/tidb-community-server-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.org/tidb-community-server-{version}-linux-amd64.tar.gz.sha256` |
-| `https://download.pingcap.org/tidb-community-server-{version}-linux-arm64.tar.gz` (pd-ctl) | Linux | arm64 | `https://download.pingcap.org/tidb-community-server-{version}-linux-arm64.tar.gz.sha256` |
+| `https://download.pingcap.com/tidb-community-server-{version}-linux-amd64.tar.gz` (pd-ctl) | Linux | amd64 | `https://download.pingcap.com/tidb-community-server-{version}-linux-amd64.tar.gz.sha256` |
+| `https://download.pingcap.com/tidb-community-server-{version}-linux-arm64.tar.gz` (pd-ctl) | Linux | arm64 | `https://download.pingcap.com/tidb-community-server-{version}-linux-arm64.tar.gz.sha256` |
 
 > **Note:**
 >
-> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-server-v8.5.0-linux-amd64.tar.gz`.
+> `{version}` in the link indicates the version number of TiDB. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-server-v8.5.0-linux-amd64.tar.gz`.
 
 ### Compile from source code
 
diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md
index aa9ab0fbe37a4..7701888c21071 100644
--- a/production-deployment-using-tiup.md
+++ b/production-deployment-using-tiup.md
@@ -82,16 +82,16 @@ Perform the following steps in this section to deploy a TiDB cluster offline usi
 **Method 1**: Download the offline binary packages (TiUP offline package included) of the target TiDB version using the following links. You need to download both the server and toolkit packages. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/).
 
 ```
-https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz
+https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz
 ```
 
 ```
-https://download.pingcap.org/tidb-community-toolkit-{version}-linux-{arch}.tar.gz
+https://download.pingcap.com/tidb-community-toolkit-{version}-linux-{arch}.tar.gz
 ```
 
 > **Tip:**
 >
-> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v8.5.0-linux-amd64.tar.gz`.
+> `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v8.5.0-linux-amd64.tar.gz`.
 
 **Method 2**: Manually pack an offline component package using `tiup mirror clone`. The detailed steps are as follows:
 
diff --git a/upgrade-monitoring-services.md b/upgrade-monitoring-services.md
index 572c450d7be07..a02e574e645a9 100644
--- a/upgrade-monitoring-services.md
+++ b/upgrade-monitoring-services.md
@@ -31,12 +31,12 @@ Download a new installation package from the [Prometheus download page](https://
 1. Download the TiDB server package and extract it. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/).
 
     ```
-    https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz
+    https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz
     ```
 
     > **Tip:**
     >
-    > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-{{{ .tidb-version }}}-linux-amd64.tar.gz`.
+    > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `{{{ .tidb-version }}}` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-{{{ .tidb-version }}}-linux-amd64.tar.gz`.
 
 2. In the extracted files, locate `prometheus-v{version}-linux-amd64.tar.gz` and extract it.
 
@@ -80,12 +80,12 @@ In the following upgrade steps, you need to download the Grafana installation pa
 1. Download the TiDB server package and extract it. Note that your downloading means you agree to the [Privacy Policy](https://www.pingcap.com/privacy-policy/).
 
     ```
-    https://download.pingcap.org/tidb-community-server-{version}-linux-{arch}.tar.gz
+    https://download.pingcap.com/tidb-community-server-{version}-linux-{arch}.tar.gz
     ```
 
     > **Tip:**
     >
-    > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.org/tidb-community-toolkit-v8.5.0-linux-amd64.tar.gz`.
+    > `{version}` in the link indicates the version number of TiDB and `{arch}` indicates the architecture of the system, which can be `amd64` or `arm64`. For example, the download link for `v8.5.0` in the `amd64` architecture is `https://download.pingcap.com/tidb-community-toolkit-v8.5.0-linux-amd64.tar.gz`.
 
 2. In the extracted files, locate `grafana-v{version}-linux-amd64.tar.gz` and extract it.