Public Vercel evidence we can test
Vercel is relevant here for custom domains, A/CNAME records, apex/wildcard behavior and certificates. The scanner does not sign in to the account; it compares the public-facing configuration associated with Domains, DNS records, verification, SSL provisioning so a provider dashboard and the Internet-visible result can be checked against one another.
- Domains — Verify Domains from the public Internet and compare it with the value the responsible provider says should be live.
- DNS records — Verify DNS records from the public Internet and compare it with the value the responsible provider says should be live.
- Verification — Verify verification from the public Internet and compare it with the value the responsible provider says should be live.
- SSL provisioning — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.
Where Vercel changes normally belong
Vercel Project Settings > Domains together with the DNS provider that publishes the domain records. Before editing that area, verify that Vercel actually controls the failing layer; a domain may use a different company for authoritative DNS, mail or the origin application.
How to interpret Vercel detection
Domains and DNS records can support a Vercel identification, but signatures are confidence-weighted. If the visible address belongs to a CDN/reverse proxy, the edge provider is reported as the edge and the hidden origin is not guessed. Mail-provider signatures likewise identify public routing, not private account ownership.
Common Vercel change points
custom domains, A/CNAME records, apex/wildcard behavior and certificates most often breaks after a domain connection, nameserver move, website migration, certificate/HTTPS change or mail-DNS edit. For this provider, compare Domains, DNS records, verification with the value expected for the exact domain and account before replacing a working setting elsewhere.
Repair Vercel without widening the incident
Save the current public value, change only the setting tied to the diagnosis, and preserve unrelated working records. If DNS is not authoritative at Vercel, make the DNS edit at the provider named by the active nameservers. If Vercel owns only hosting or mail, leave the other service layers where they are.
Verify the Vercel repair
HTTPS should complete for the exact hostname, the certificate should be valid for that hostname, and root/www should follow the intended canonical redirect without a TLS error. The verification should use the exact hostname/service repaired and should no longer depend on a control-panel “connected” indicator once the public check is available.
What a public scan cannot see inside Vercel
Billing state, private support actions, unpublished incidents, private origin addresses and authenticated account settings are outside a public diagnostic. HostWithShery reports those areas as unknown or a next support step instead of manufacturing certainty from a weak Vercel signature.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.