Hosting Detection

How this hosting checker finds who is hosting a website

Enter a domain or any page URL and the hosting checker takes the host name from it and runs three lookups. First it resolves the domain to an IP address (the DNS A record, first IPv4). Then it reads the reverse DNS record of that IP — the Hostname row, set by whoever owns the server, such as static.12.34.56.78.clients.your-server.de. Third, it fetches the domain's nameservers (NS), which tell you who runs its DNS zone. The IP is then looked up in a geolocation database for country, city, ISP and autonomous system number (ASN).

The provider name in the large card comes from matching the NS, ISP and hostname against a list of about twenty well-known companies: Cloudflare, Amazon AWS, Google Cloud, Microsoft Azure, DigitalOcean, Hetzner, OVH, Vultr, Linode/Akamai, GoDaddy, Namecheap, Bluehost, HostGator, SiteGround, Hostinger, Vercel, Netlify, Fly.io, Render, Timeweb, REG.RU and Beget. If none matches, you get "Unknown provider" — and the ISP and ASN rows become your source of truth.

How to read the result: four common patterns

The rule of thumb: the provider label is a hint; ISP and ASN are facts about who owns the IP. When they disagree, trust the ISP. Open the AS number in the ASN lookup to see every network that company announces; the link between IP, ASN and website is explained in ASN and a website's IP address.

Finding the real host behind Cloudflare or a CDN

When a website runs through Cloudflare's proxy or another CDN, no public web host lookup can show the origin server — hiding it is the point of a reverse proxy. Indirect clues sometimes exist:

• Email. MX records often point to the same hosting account as the site, especially on shared hosting with cPanel or Plesk.
• Subdomains. mail., ftp., cpanel. or dev. are frequently left unproxied and resolve straight to the server. Check them here or with the DNS lookup.
• SPF. The SPF record sometimes lists the IP of a mail server that sits next to the website.

To report phishing, malware or copyright infringement you don't need the origin IP: Cloudflare has an official abuse form and forwards reports to the hosting provider.

Why check what hosting a website uses

• Migrations and DNS changes. After moving a site, confirm the domain already returns the new IP. If you still see the old one, the A record wasn't updated or the old value is still cached by resolvers until its TTL expires.
• Competitor research. See what the leaders in your niche run on: dedicated servers, a cloud provider, a platform such as Vercel or Netlify, or budget shared hosting.
• IP neighbours. On shared hosting hundreds of sites share one IP. A reverse IP lookup lists them. A shared IP doesn't hurt SEO by itself, but it's worth knowing if the neighbourhood is full of spam.
• Latency for your audience. A server in Europe serving visitors in Australia adds round-trip time to every uncached request. A CDN solves this for static assets.
• Abuse and legal requests. The hosting provider is the place to send abuse reports when the site owner doesn't respond.

Does server location affect SEO?

Only slightly. Google infers a site's target country mainly from the country-code domain (.co.uk, .de, .pl), content language, hreflang and links. Server location is a weak signal, and with a CDN it means little anyway, because visitors are served from the nearest edge. What matters far more for rankings is server reliability and response time: frequent 5xx errors reduce crawl rate and can drop pages from the index.

Keep in mind that IP geolocation comes from registry and network databases, not GPS. For large clouds and CDNs, the city may reflect where the network block is registered rather than the physical data centre.

What the Hostname row tells you

Reverse DNS (PTR) records are set by whoever controls the IP block, so the hostname often reveals the data centre even when there's no provider label:

• static.…clients.your-server.de — Hetzner;
• ip-51-….eu, vps-….vps.ovh.net — OVH;
• ec2-…compute.amazonaws.com — an Amazon EC2 instance;
• ….bc.googleusercontent.com — Google Cloud;
• a name on the site's own domain (server1.example.com) — the owner rents the server and set the PTR themselves.

If the Hostname row just repeats the IP address, no PTR record exists — common on budget VPS plans and CDNs. Anyone renting a dedicated server or VPS can set any name, so treat the PTR as a hint and confirm network ownership with the ASN.

When the hosting lookup returns nothing

• "Could not resolve domain". There is no IPv4 A record: the domain isn't delegated, has expired, is IPv6-only, or the address has a typo. Inspect its records with the DNS lookup.
• No NS row. Nameserver records exist only at the zone apex. www.example.com or blog.example.com have none — enter the bare domain example.com.
• No country, ISP or ASN. The geolocation database didn't answer within 3 seconds. Try again in a minute.
• www and non-www return different IPs. They are separate DNS records. If the www version still points to an old host, visitors may see two different sites — fix the records and 301-redirect to one canonical version.

Web host vs. registrar vs. DNS provider

These are often three different companies. A domain can be registered at Namecheap, use Cloudflare for DNS and be hosted on a Hetzner server. A hosting checker answers "where is the server". To see the registrar and expiry date, use the WHOIS lookup. If it's your site and you're moving it, change the A record wherever the nameservers point — not at the registrar if DNS is managed by a separate service.