tencent cloud

Domains

Release Notes and Announcements
Announcements
Product Introduction
Overview
Strengths
Domain Suffixes
Introduction to Domain Name Registrars
Product Rules
Rules for 60-Day Inter-Registrar Transfer Lock
Domain Transfer-Out Rules
Domain Naming Rules
Purchase Guide
Purchase Method
Domain Registration
Registration Guide
.ai Domain Registration
Domain Management
Domain Renewal
Enabling Domain Security Protection
Mobile and Email Verification
Modifying DNS Servers
Domain Redemption
Custom DNS Host
Modifying Registrant Profile
Domain Registrant Profile
Managing Domain Expiration Reminders
Domain Lookup
Domain Status
Batch Operation
Batch Domain Renewal
Bulk Modifying DNS Servers
Batch Setting Update Prohibition Lock for Domains
Batch Setting Transfer Prohibition Lock for Domains
Domain Transfer
Cross-Account Domain Transfer
Domain Transfer Out
Domain Transfer In
Domain Push
Troubleshooting
Domain Registration
Domain Transfer-In
API Documentation
History
Introduction
API Category
Making API Requests
Domain Management APIs
Domain Query APIs
Bulk Operation APIs
Registrant Profile APIs
Other APIs
Data Types
Error Codes
FAQs
Domain Registration
Domain Transfer
Domain Renewal
Domain Transfer-In
DNS Settings
Cross-Account Domain Transfer
Domain Security
DNS Abuse Complaints
Product Policy
Privacy Policy
Data Processing And Security Agreement
Domain Name Registration Service Agreement
TLD registry policies

Request Structure

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-10-30 21:40:53

1. Service Address

The API supports access from either a nearby region (at domain.intl.tencentcloudapi.com) or a specified region (at domain.ap-guangzhou.tencentcloudapi.com for Guangzhou, for example).

We recommend using the domain name to access the nearest server. When you call an API, the request is automatically resolved to a server in the region nearest to the location where the API is initiated. For example, when you initiate an API request in Guangzhou, this domain name is automatically resolved to a Guangzhou server, the result is the same as that of specifying the region in the domain like "domain.ap-guangzhou.tencentcloudapi.com".

Note: For latency-sensitive businesses, we recommend that you specify the region in the domain name.

Tencent Cloud currently supports the following regions:

Hosted region Domain name
Local access region (recommended, only for non-financial availability zones) domain.intl.tencentcloudapi.com
South China (Guangzhou) domain.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) domain.ap-shanghai.tencentcloudapi.com
East China (Nanjing) domain.ap-nanjing.tencentcloudapi.com
North China (Beijing) domain.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) domain.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) domain.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) domain.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) domain.ap-singapore.tencentcloudapi.com
Southeast Asia (Jakarta) domain.ap-jakarta.tencentcloudapi.com
Southeast Asia (Bangkok) domain.ap-bangkok.tencentcloudapi.com
Northeast Asia (Seoul) domain.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) domain.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) domain.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) domain.na-siliconvalley.tencentcloudapi.com
South America (São Paulo) domain.sa-saopaulo.tencentcloudapi.com
Europe (Frankfurt) domain.eu-frankfurt.tencentcloudapi.com

2. Communications Protocol

All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communication tunnels.

3. Request Methods

Supported HTTP request methods:

  • POST (recommended)
  • GET

The Content-Type types supported by POST requests:

  • application/json (recommended). The TC3-HMAC-SHA256 signature algorithm must be used.
  • application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature algorithm must be used.
  • multipart/form-data (only supported by certain APIs). You must use TC3-HMAC-SHA256 to calculate the signature.

The size of a GET request packet is up to 32 KB. The size of a POST request is up to 1 MB when the HmacSHA1 or HmacSHA256 signature algorithm is used, and up to 10 MB when TC3-HMAC-SHA256 is used.

4. Character Encoding

Only UTF-8 encoding is used.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan