Hosting Checker

Resolve a domain's IP address, nameservers and mail servers to work out who hosts it.

How this hosting checker works

The tool runs three DNS lookups from our server and shows you the raw answers: the domain's IPv4 address (its A record), its NS records, which name the authoritative nameservers, and its MX records, which name the servers that accept its email. It does not consult a hosting database or a list of provider IP ranges. The "who hosts it" part is an inference you draw from those three names, and the sections below show how.

Take edeskcloud.com, which we ran through the tool on 11 October 2026. The A record pointed to 82.25.87.1, the nameservers were derek.ns.cloudflare.com and hope.ns.cloudflare.com, and the MX records were mx1.hostinger.com and mx2.hostinger.com. Read together: DNS is managed at Cloudflare, mail is handled by Hostinger, and a reverse IP lookup on 82.25.87.1 returned us-bos-web1978.main-hosting.eu, a name in Hostinger's server network. So the site is hosted at Hostinger, even though the nameservers say Cloudflare.

Nameservers tell you who runs the DNS zone, which is often the registrar or a CDN rather than the web host. MX records tell you who receives the domain's email, frequently a third company such as Google Workspace (aspmx.l.google.com) or Microsoft 365 (hostnames ending in mail.protection.outlook.com). Only the A record points at the machine that serves the website, and even that can mislead, as the next section explains. To learn which network owns the address and its autonomous system number, paste the IP into the IP address lookup.

When the result hides the real host

The site sits behind a CDN or reverse proxy. When a domain is proxied through Cloudflare, Fastly, Akamai or Amazon CloudFront, its A record points to the proxy's edge address and the origin server's address is not published anywhere in DNS. Cloudflare's documentation describes how requests reach its network first and only then travel to the origin (How Cloudflare works). Our own tools.edeskcloud.com is an example: the tool resolves it to 172.67.201.105, a Cloudflare address, and nothing in the answer reveals the Hostinger server behind it. In that situation DNS alone cannot identify the host, and this tool will not pretend otherwise.

You looked up a subdomain. NS records live at the top of a zone. tools.edeskcloud.com returns an IP but no NS or MX records, because the subdomain has no delegation of its own. Look up the parent domain for the nameservers.

The host is IPv6-only, or the name does not resolve. The tool resolves IPv4 addresses only. A domain with only an AAAA record, an expired domain or a typo returns "Could not resolve domain."

www and the bare domain differ. www.example.com may be a CNAME to a hosting platform while example.com points somewhere else. Enter the exact hostname you are interested in.

Null MX. A domain that publishes an MX record of "0 ." is declaring that it accepts no email at all (RFC 7505). example.com does this, and the tool shows it as a record with priority 0 and an empty server name.

Nameserver names you will see often

Providers use recognisable patterns for their nameservers. Matching the NS records against this list usually identifies the DNS provider; whether that company also hosts the website is a separate question, answered by the IP address.

Provider Nameserver pattern What it usually means
Cloudflare*.ns.cloudflare.comDNS at Cloudflare; hosting anywhere
AWS Route 53ns-*.awsdns-*.com / .net / .org / .co.ukDNS at AWS; hosting often, not always, on AWS
Google Cloud DNSns-cloud-*.googledomains.comDNS at Google Cloud
GoDaddyns*.domaincontrol.comRegistrar default DNS; hosting may be GoDaddy or elsewhere
Namecheapdns*.registrar-servers.comRegistrar default DNS
DigitalOceanns*.digitalocean.comDNS at DigitalOcean; usually a droplet hosts the site
Bluehostns*.bluehost.comShared hosting with DNS at the host
Hetzner*.ns.hetzner.comDNS at Hetzner; dedicated or cloud server
OVHclouddns*.ovh.net and ns*.ovh.netDNS at OVHcloud; dedicated or cloud server

Mail follows the same idea: aspmx.l.google.com means Google Workspace, a name ending in mail.protection.outlook.com means Microsoft 365, and MX records under the same company as the A record usually mean the web host also runs the mailboxes.

Frequently Asked Questions

Do Cloudflare nameservers mean Cloudflare hosts the site?

No. Cloudflare provides DNS for every domain on its service and, optionally, a proxy in front of the site. Only sites on Cloudflare Pages or Workers are actually hosted there. The IP address in the result tells you which case you have: an address in Cloudflare's own ranges means the proxy is on and the host is hidden, while any other address is the host's own server, as with edeskcloud.com above.

What are nameservers?

Nameservers are the DNS servers that hold the authoritative records for a domain, as defined in RFC 1034. Your registrar records them at the registry, and every resolver on the internet ends up asking them for your A, MX and other records. The same names also appear in the domain's WHOIS record.

Why check who hosts a website?

Three reasons come up most. You are choosing a provider and want to see what comparable sites use. You are migrating a site and need an inventory of its A, NS and MX records before anything changes. Or a site is down, or abusive, and you need to know which company to contact; for abuse, the network owner shown by the IP address lookup is the right party.

Why does the tool say it could not resolve the domain?

The name has no IPv4 address. That happens with a typo, an expired or parked domain that has lost its records, a brand-new domain whose DNS has not been set up yet, or a host reachable over IPv6 only. The DNS checker can show whether an AAAA or CNAME record exists instead.