Measured nightly · state as of 2026-10-19
Does Domain Chief support Domain Connect?
Serves 5 of 5 DoDomain templates. The connect flow offers the provider's one-click approval for these, 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.
Every row below is the nightly watch's own measurement of Domain Chief's Domain Connect API, not a claim the provider made to us.
| Template | Measured | HTTP | Since | Version | Real apply |
|---|---|---|---|---|---|
| custom-subdomain-cname | served, apply not proven | 200 | 2026-07-28 | v1, matches registry | not proven |
| domain-verification | served, apply not proven | 200 | 2026-07-28 | v1, matches registry | not proven |
| custom-subdomain-cname-with-verification | served, apply not proven | 200 | 2026-09-11 | v1, matches registry | not proven |
| apex-a-with-verification | served, apply not proven | 200 | 2026-09-11 | v1, matches registry | not proven |
| email-authentication | served, apply not proven | 200 | 2026-09-11 | v1, matches registry | 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 domain.chief.app/api/domainconnect. Control probe google.com/domain-verification answered 200.
Frequently asked questions
Does Domain Chief support Domain Connect?
Domain Chief'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: Serves 5 of 5 DoDomain templates. The connect flow offers the provider's one-click approval for these, 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.
Is setup one-click when a customer's domain is at Domain Chief?
The connect flow offers Domain Chief's one-click approval for the 5 templates served there, but DoDomain has not yet proven an end-to-end apply on Domain Chief, so it does not promise it. If an apply fails the flow falls back to guided manual records, verified against the authoritative nameservers.
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.
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.
No apply has been proven at Domain Chief, so the state page ledger lists none.
Start on the free plan
No card, no sales call: create an app, mint a session, and watch the first domain verify.