Free tools
DNS provider detector
Type a domain and see which DNS host serves it, which connect path a custom-domain setup would take there, and whether that host has onboarded one-click Domain Connect templates. The same engine DoDomain runs for every customer domain, read from the zone's own nameservers.
What this check does not tell you
It does not read existing records at the names a setup would write, it does not check CAA, SPF or DMARC (the SPF checker does that), it does not say whether the provider flattens a CNAME at the apex, and it does not say whether the domain is registered or resolving. It answers one question — who serves this zone, and what can be done there — and stops.
Frequently asked questions
How does the detector know which DNS provider a domain uses?
It resolves the zone's authoritative NS records — the nameservers the registry delegates the domain to — and matches them against known provider nameserver patterns (Cloudflare, GoDaddy, Namecheap, Google Domains/Squarespace, Route 53, Vercel and others). When no pattern matches, it asks the zone's _domainconnect TXT record, through which a Domain Connect provider names itself. The nameservers are shown so you can check the match yourself.
What does one-click DNS setup mean here?
Two mechanisms let a product write DNS records for a user without the user editing records by hand: Cloudflare OAuth, where the user grants access once and records are written through Cloudflare's API, and Domain Connect, an open protocol where the user approves a template at their DNS host. The detector reports which of the two applies, or that the domain takes the guided manual path.
Why does a template row say not probed instead of yes or no?
Because we did not ask. A template is only probed when the domain takes the Domain Connect path and its provider published a discovery record; when the provider is too slow to answer, that is reported as a fact about our request, not about the provider. A red mark next to something we never measured would be a claim about someone else's product that we invented.
Is the result cached?
No. Every check is a live lookup against the zone's authoritative nameservers and, for Domain Connect zones, a live request to the provider's API. Change your nameservers and re-run the check to see the new answer.
More free tools
- DNS propagation checker
One record, read from the authoritative nameservers and three public resolvers.
- SPF record checker
Parse a domain's SPF, walk its includes, count the lookups against the limit of ten.