Your website & domain

Connect your own domain

Last updated 2026-07-08

Every DiveConnect site is live right away on a free subdomain like yourshop.diveconnect.ai. When you're ready, you can point a domain you already own — like www.yourshop.com — at your DiveConnect site. Your site, bookings, and SSL certificate all keep working; visitors just see your own address.

Before you start

• Your registrar login. That's the company you bought the domain from — GoDaddy, Namecheap, Cloudflare, Google Domains, etc. You'll add two DNS records there.
• Your domain entered in DiveConnect. In the dashboard, go to Website → Domain and enter the domain you want to connect. This tells us to expect it and issue the SSL certificate.
• 10 minutes. The records take a minute to add; the internet can take a little while to notice (usually ~15 minutes, occasionally up to 48 hours).

The two DNS records

Add both records at your registrar so your site works with and without the www:

Your email keeps working. These records only route your website. Email uses different records (MX) which you are not touching — do not delete or change any MX, TXT, or other existing records.

Step-by-step by registrar

GoDaddy

1. Log in and open the Domain Control Center (My Products → your domain).
2. Select Manage DNS.
3. Click Add and create the A record: Name @, Value 76.76.21.21, TTL default. Save.
4. Click Add again and create the CNAME: Name www, Value cname.vercel-dns.com. Save.
5. If an old A record for @ or CNAME for www already exists (pointing at your old site), edit it to the new value instead of adding a duplicate.

Namecheap

1. Log in → Domain List → Manage next to your domain.
2. Open the Advanced DNS tab.
3. Add New Record → A Record: Host @, Value 76.76.21.21. Save.
4. Add New Record → CNAME Record: Host www, Value cname.vercel-dns.com. Save.
5. Remove or edit any conflicting old records for the same hosts (e.g. Namecheap's default "parking page" redirect).

Cloudflare

1. Log in and select your domain → DNS.
2. Add record → Type A, Name @, IPv4 76.76.21.21.
3. Add record → Type CNAME, Name www, Target cname.vercel-dns.com.
4. Set the cloud icon on both records to DNS only (grey cloud, proxy off). Cloudflare's orange-cloud proxy in front of our SSL causes certificate errors.

Using a different registrar? The records are identical everywhere — find the DNS settings page and add the same A and CNAME records above.

Verify it worked

1. Back in the dashboard, open Website → Domain.
2. Click Verify DNS. It checks both records and shows what we see live.
3. Once verified, we issue your SSL certificate automatically. Your site is then live at your domain over https:// — nothing else to configure.

Troubleshooting

• "Verify DNS" still failing after an hour? Check for duplicate records: an old A record on @ or a second CNAME on www pointing somewhere else wins randomly. Keep exactly one of each, with the values above.
• Certificate error in the browser? On Cloudflare, make sure both records are DNS only (grey cloud). Elsewhere, wait a few minutes — the certificate is issued right after DNS verifies.
• Site works at www but not the bare domain (or vice versa)? One of the two records is missing — you need both the A and the CNAME.
• Email stopped arriving? An MX record was probably deleted while editing. Restore your registrar's previous MX records — DiveConnect never needs them changed.
• Domain bought through a website builder (Wix, Squarespace, Shopify)? You may need to unlock DNS editing or transfer DNS to the registrar first — their support article for "pointing your domain elsewhere" covers it.

Moving from an existing website?

Your old site stays live until the DNS change propagates, so there's no downtime window to plan around. Two tips for a smooth handover:

• Publish your DiveConnect site first and check it at your *.diveconnect.ai subdomain before switching DNS.
• Keep your old hosting active for a week after the switch, in case you need to grab any content or images you forgot.

Need a hand? Email us at admin@diveconnect.io or open a ticket from your dashboard under Support — we usually reply within one business day.