Custom domain TLS handshake resets before ServerHello (.vercel.app works, DNS verified)

Hi everyone,

I'm experiencing a TLS handshake issue with my custom domain that I haven't been able to resolve.

Setup

Project: mehboob-scales.vercel.app ✅ Works
Custom domain: www.mehboobscales.com ❌ Fails
Plan: Hobby
Registrar/DNS: GoDaddy

What I've verified

✅ Domain attached to Production deployment
✅ Dashboard shows Valid Configuration
✅ SSL certificate is shown as issued
✅ DNS matches Vercel's recommended configuration (vercel-dns-017.com)
✅ Removed/re-added the domain multiple times
✅ Redeployed the project

TLS behavior

curl -Iv https://www.mehboobscales.com

1Connected to xx.xx.xx.xx:4432TLS handshake, Client hello3Recv failure: Connection reset by peer

openssl s_client -connect www.mehboobscales.com:443 -servername www.mehboobscales.com

1CONNECTED2no peer certificate available3SSL handshake has read 0 bytes and written 1552 bytes

The server never sends a ServerHello or certificate.

Official Vercel debug script

I ran the official vercel-connect-debug script.

Results:

✅ DNS resolution correct
✅ TCP connectivity succeeds
✅ Ping succeeds
❌ Every advertised Vercel edge IP resets the TLS handshake immediately after the ClientHello

I've attached the complete debug log.

Additional information

mehboob-scales.vercel.app works perfectly.
Same issue on macOS, Android, Chrome, Safari, PTCL and Jazz.
External uptime tools report the site as online.

Could someone from the Vercel team please verify whether the hostname for www.mehboobscales.com is correctly provisioned on the edge and whether the TLS certificate is actually attached to the hostname?

Thank you!