DNS provider lookup
Looks up the NS set through the public resolvers and matches each name server name against a fixed, versioned list of DNS providers, such as Cloudflare, Route 53, Azure DNS and Google Cloud DNS. Name servers of several providers are reported as information. The name servers themselves are not contacted.
Updated 2026-10-28
What this tool checks
The NS records are looked up through public resolvers, and each name server name is matched against a fixed list of DNS providers (Cloudflare, Amazon Route 53, Azure DNS, Google Cloud DNS, GoDaddy, Namecheap, NS1, Hetzner, OVHcloud and more):
- Providers: each provider with the name servers that matched it.
- Unknown: name servers that match no provider on the list.
- Several providers: reported as information.
How to read the result
The table lists every name server with its provider. The list version is shown, so you know which patterns were used.
Limitations
- The provider is read from the names alone. A provider that serves a zone on name servers named after the customer's own domain is not recognised.
- The name servers are not asked, so whether they really answer for the zone is not checked; the name server check looks at their addresses.
Use it from code
API reference for DNS provider lookup
curl -i "https://api.lookproof.dev/v1/dns/ns-provider?domain=example.com"A request without payment is answered with 402 Payment Required and the exact price. See the API reference.
Limits
| Input | Domain |
|---|---|
| Deadline | 10 seconds |
| Freshness | Up to 5 minutes, never longer than the record TTL |
| Price | $0.01 per check |
Findings this tool can report
DNS (3)
- Error
DNS_DOMAIN_NOT_FOUNDThe DNS resolver reported that the domain does not exist. - Warning
DNS_RESOLVER_FAILUREThe DNS resolver returned a server failure. - Warning
DNS_RESOLVER_TIMEOUTThe DNS resolver did not answer in time.
Check (1)
- Warning
CHECK_QUERY_BUDGET_EXCEEDEDThe check stopped after reaching its DNS query limit.
Name servers (3)
- Warning
NS_NOT_FOUNDThe name has no NS records. - Info
NS_PROVIDER_MULTIPLEThe name servers belong to more than one DNS provider. - Info
NS_PROVIDER_UNKNOWNA name server matches none of the DNS providers on the list.
Frequently asked questions
How is the provider found?
From the names in the domain's NS records. Each provider names its name servers in a fixed way, such as ada.ns.cloudflare.com or ns-123.awsdns-45.com, and the tool matches the names against a list of those patterns.
What if a name server is not recognised?
It is listed as unknown with NS_PROVIDER_UNKNOWN. It can be the domain's own server, a registrar's or a provider that is not on the list; that is information, not a problem.
Is it a problem to use two providers?
Not necessarily: some zones are served by two providers on purpose. After a move it can also be a leftover, where the old provider still answers with old data. NS_PROVIDER_MULTIPLE points it out.