My Vercel-hosted author website is inaccessible over HTTPS on multiple Wi-Fi networks, although it works over cellular data.
Domain: https://theworldendspolitely.xyz
Project: love-and-other-malfunctions-funnel
Working Vercel URL: https://love-and-other-malfunctions-funnel.vercel.app
Symptoms
- Chrome and Edge return ERR_SSL_PROTOCOL_ERROR.
- The problem occurs on home and workplace Wi-Fi.
- The custom domain works on cellular data.
- Edge InPrivate mode produces the same error.
- The default vercel.app domain works normally.
Diagnostics already completed
Vercel reports:
- Valid domain configuration
- Production assignment
- Active CDN
- Two automatically managed SSL certificates expiring January 17 and 19, 2027
Google DNS returns:
- 216.198.79.1
- 64.29.17.1
Windows PowerShell:
Test-NetConnection theworldendspolitely.xyz -Port 443
Result: TcpTestSucceeded: True
HTTPS requests using curl.exe fail during the TLS handshake:
SEC_E_INVALID_TOKEN (0x80090308)
Explicitly testing both Vercel IP addresses produces the same error.
Disabling ECH did not resolve the issue.
Security classification findings
VirusTotal reported 0/93 malicious detections, although Forcepoint ThreatSeeker separately labeled the site Suspicious.
Forcepoint Site Lookup classifies the domain as Elevated Exposure in both its database and real-time categories. Its detailed report describes a possible compromised website, with Low threat severity.
This may be a false positive, but it has not yet been independently verified.
Previous Vercel support response
Vercel's automated support agent reported that DNS, SSL issuance, certificate delivery, and HTTP responses were healthy from its testing environment.
It suggested that network security filtering might be interrupting the TLS handshake.
Assistance requested
Could someone from Vercel help determine:
- Whether the observed TLS failures are caused by network filtering, edge routing, or another domain-specific issue.
- Whether Vercel has additional diagnostics to identify why both IP addresses fail from affected connections.
- Whether the Forcepoint Elevated Exposure classification may be contributing to the failures.
- Whether any corrective action is necessary on the Vercel side.
I would appreciate assistance identifying and resolving the underlying problem rather than making additional speculative configuration changes.
This is a public author website, and visitors using affected networks cannot access it.