Custom domain and HTTPS

I want to attach my own domain with HTTPS to an already-deployed project.

Current state:
- Hosted on: {{e.g. Vercel / my own server}}
- Domain registrar: {{e.g. Namecheap / Alibaba Cloud}}
- Domain: {{yours}}
- Target: {{www.yourdomain.com or yourdomain.com}}

Please give me:
1. The DNS records to add (type, host, value) and what each one does.
2. What to configure on the hosting platform.
3. How to get an HTTPS certificate (automatic or manual), and how if not automatic.
4. Roughly how long propagation takes and how to verify.
5. Common traps: DNS not resolving, certificate issuance failing, www vs non-www.

Rules:
- Explain what each record does. I do not want to paste config without understanding it.
- For servers in mainland China, remind me about ICP filing - unfiled domains can be blocked on ports 80/443.

Replace the {{}} parts with your own content

Why it works

1. Explaining each record keeps you able to debug instead of blindly pasting config
2. Separating automatic from manual certificates matters because most platforms auto-issue, so no manual hassle is needed
3. Proactively raising ICP filing catches a mainland-China-only constraint you would otherwise hit after deploying
4. Stating propagation time and verification stops you from assuming a correct config failed

What it looks like

Pointing a domain at a Vercel site, AI gives the CNAME record, the platform-side domain add, automatic certificate issuance, and notes DNS propagation can take minutes to hours.

Where it bites

• !Refreshing right after a DNS change and assuming failure, then churning the config when it just needed time
• !Binding a domain to a mainland-China server without filing, so ports 80/443 are blocked no matter what you configure

Browse categories