Measured nightly · state as of 2026-10-19
Does Vercel support Domain Connect?
One-click setup is proven on 1 of 5 DoDomain templates. 1 more is served there with no end-to-end apply proven yet. The connect flow offers the provider's one-click approval for it, but DoDomain has not yet proven an end-to-end apply on this provider, so it does not promise it; if an apply fails the flow falls back to guided manual records verified the same way. The other 3 use guided manual records, verified against the authoritative nameservers.
Every row below is the nightly watch's own measurement of Vercel's Domain Connect API, not a claim the provider made to us.
| Template | Measured | HTTP | Since | Version | Real apply |
|---|---|---|---|---|---|
| custom-subdomain-cname | one-click, proven | 200 | 2026-10-15 | v1, matches registry | proven 2026-10-20 |
| domain-verification | served, apply not proven | 200 | 2026-10-15 | v1, matches registry | not proven |
| custom-subdomain-cname-with-verification | not served | 404 | n/a | n/a | not proven |
| apex-a-with-verification | not served | 404 | n/a | n/a | not proven |
| email-authentication | not served | 404 | n/a | n/a | not proven |
Measured state as of 2026-10-19 12:18 UTC (the date the state last changed; the watch probes every night and writes only when something moves) against vercel.com/api/domain-connect. Control probe google.com/domain-verification answered 200.
Frequently asked questions
Does Vercel support Domain Connect?
Vercel's Domain Connect API answered the control probe with 200 in the measured state dated 2026-10-19, so a missing template there is a real answer. For DoDomain's 5 templates: One-click setup is proven on 1 of 5 DoDomain templates. 1 more is served there with no end-to-end apply proven yet. The connect flow offers the provider's one-click approval for it, but DoDomain has not yet proven an end-to-end apply on this provider, so it does not promise it; if an apply fails the flow falls back to guided manual records verified the same way. The other 3 use guided manual records, verified against the authoritative nameservers.
Is setup one-click when a customer's domain is at Vercel?
Proven for 1 of 5 templates: a real signed apply was accepted by Vercel and the record verified on a zone DoDomain controls. Templates served there but not yet proven are offered in the connect flow without a promise; Anything not served uses guided manual records.
How is this measured?
A scheduled job asks the provider's Domain Connect API for a widely onboarded control template, then for each DoDomain template. A 404 is only believed when the control answers 200. The result is committed as a JSON file and this page is rebuilt from it.
Manual setup at Vercel
Wherever a template falls back to manual records, the connect flow shows Vercel steps beside the exact records to create, and verifies each record against the zone's authoritative nameservers. Enter the record name as the prefix only (e.g. `www`); leave it empty for the apex.
The full walkthrough is Vercel CNAME and A record setup.
Keep reading
The whole provider matrix is the state of Domain Connect. To see which provider serves any domain you type in, use the provider detector. New to the protocol? Domain Connect, defined.
The dated note on each proven Vercel apply is in the proven applies ledger on the state page.
Start on the free plan
No card, no sales call: create an app, mint a session, and watch the first domain verify.