How to check website hosting details in six lookups
To check website hosting details, you work from the domain name down to the server: resolve the domain to an IP address, then look up who holds that IP block in the regional internet registry. The organisation holding the block is usually the hosting company or the data centre network it rents from. Nameservers, MX records and HTTP headers fill in the rest, but each answers a different question, so it pays to know what every lookup actually tells you.
The examples below use example.com and the documentation address 203.0.113.10. Both are reserved for documentation (RFC 5737), so registries return no real owner for them; swap in the site you are checking. The commands run on Linux and macOS (on Ubuntu or Debian, install dig and whois with sudo apt install dnsutils whois if they are missing). Windows 10 and 11 include nslookup and curl.exe; in Windows PowerShell 5.1, type curl.exe, because plain curl is an alias for Invoke-WebRequest.
Quick checklist
- Find the IP:
dig +short example.com A(ornslookup example.com). - Look up who holds the IP:
whois 203.0.113.10or an RDAP query to the right registry. - Note the ASN (the network number) and its name.
- Check nameservers with
dig NS: this is the DNS provider, not necessarily the host. - Check MX records: this is the email provider.
- Read the HTTP headers with
curl -sI. - If the IP belongs to a CDN such as Cloudflare, stop there: the origin host is deliberately hidden.
Step 1: find the website's IP address
The host is wherever the domain's A record (IPv4) or AAAA record (IPv6) points. Ask DNS for it:
dig +short example.com A
dig +short example.com AAAA
dig +short www.example.com A
Check www separately, because it is often a CNAME to a different service. On Windows, nslookup example.com prints the same addresses. ping example.com also shows the IP it resolved, even when the server ignores the ping itself. If the lookup fails with NXDOMAIN, the domain has no working DNS at all; DNS_PROBE_FINISHED_NXDOMAIN explained covers why.
Step 2: who hosts a website? Look up the IP owner
Every public IP address is allocated through one of five regional internet registries (RIRs): ARIN for North America, RIPE NCC for Europe and the Middle East, APNIC for Asia-Pacific, LACNIC for Latin America and AFRINIC for Africa. India falls under APNIC, and IRINN, India's national internet registry, works within the APNIC system, so Indian IP ranges appear in the APNIC whois database.
This IP-owner lookup is the core of how to find hosting of a website. The quickest query is plain whois, which follows referrals to the right registry on most systems:
whois 203.0.113.10
whois -h whois.apnic.net 203.0.113.10
Read the inetnum block (the IPv4 range), its netname and descr fields, and the organisation. A large hosting company usually holds the range in its own name. A smaller one may rent servers in someone else's data centre, in which case whois shows the data centre or network provider rather than the brand you buy from.
RDAP: the structured replacement for whois
RDAP (Registration Data Access Protocol) returns the same registration data as JSON over HTTPS, in a format standardised by RFC 9083. APNIC runs a public RDAP service:
curl -s https://rdap.apnic.net/ip/203.0.113.10
If you are not sure which registry holds an address, IANA publishes a bootstrap file, https://data.iana.org/rdap/ipv4.json, that maps each range to the correct RDAP server.
Step 3: how to find website hosting provider names from the ASN
An autonomous system number (ASN) identifies the network that announces the IP block to the rest of the internet. The ASN name is often a clearer answer to "which hosting is a website using" than the inetnum, because a provider may hold many small ranges but one ASN. APNIC and RIPE whois output for an IP often includes a route object whose origin field names the ASN (ARIN shows an OriginAS field, which is sometimes empty), and you can look up the ASN itself. AS64500 below is a documentation ASN (RFC 5398):
whois -h whois.apnic.net AS64500
curl -s https://rdap.apnic.net/autnum/64500
Online IP and ASN lookup tools do the same thing behind a web form, and are a quick answer to how to check website hosting details without a terminal. They are convenient, but results are only as current as their data, so check anything important against the registry.
Step 4: nameservers show the DNS provider, not the host
A common mistake is to read the nameservers and assume they name the host:
dig +short example.com NS
Nameservers tell you who answers DNS queries for the domain. That can be the web host, but it is just as often the registrar, a CDN or a separate DNS service. The DNS and the website itself are frequently run by different companies. Comparing DNS providers is covered in the fastest DNS options for India.
Step 5: MX records show the email provider
dig +short example.com MX
MX records list the mail servers that accept email for the domain. They identify the email provider, which is frequently a different company from the web host. Do not use them to answer where a website is hosted.
Step 6: read the HTTP response headers
curl -sI https://example.com
The -I flag sends a HEAD request and prints only the response headers; -s hides the progress meter. A few servers answer HEAD differently from GET, so if the result looks odd, try curl -s -D - -o /dev/null https://example.com, which makes a normal GET and prints just the headers. Look for:
- Server: the web server software, such as
nginx,ApacheorLiteSpeed. It names the software, not the company. - X-Powered-By: sometimes reveals PHP or a framework version.
- Provider-specific headers: some hosts and CDNs add their own header names, which can identify them.
Headers are set by the server's owner and can be removed or changed, so treat them as clues rather than proof.
When a CDN hides the real host
If whois or RDAP shows the IP belongs to Cloudflare or another CDN or reverse proxy, the A record points at the CDN's edge, not the origin server. Cloudflare-proxied sites typically return server: cloudflare and a cf-ray header. What you can learn is that the site uses that CDN, plus its nameservers and MX records. What you cannot learn from public records is the origin server's address. Hiding it is a deliberate security measure against attacks, and you should not try to get around it. If you have a legitimate reason, such as an abuse report or a legal matter, use the CDN's own abuse or trust-and-safety process, which forwards reports to the hosting provider.
The registrar is not the host
Domain whois or RDAP shows the registrar, the company the domain was registered through, plus dates and nameservers. ICANN's lookup tool at lookup.icann.org returns this registration data for domain names. The registrar only manages the name; the website can sit on any server anywhere. Many domains have privacy or redaction on the registrant's details, so do not expect an owner's name.
Where is my website hosted? Checking your own site
If the question is how to find the hosting provider of your own website, the external lookups above work, but your records are faster and more reliable:
- Invoices and payment emails: search your inbox for hosting renewal invoices. The company billing you for the server or plan is your host.
- Control panel: the panel you log in to (cPanel, a VPS panel or a client area) belongs to your host, and it shows the server's IP and location.
- Nameservers at your registrar: these often point at your host's DNS, which is a strong hint, though not proof.
- Compare IPs: if the IP in your control panel matches
dig +short yourdomain.com A, the site is live on that server.
Knowing this before you move hosts saves a lot of guessing; the website migration checklist starts from exactly these details.
Use this information responsibly
Every lookup here reads public registration and DNS data, which is fine for checking a competitor's setup, reporting abuse, sending a copyright notice or planning a migration. Do not use it to probe, scan or attack servers you do not run, and do not attempt to uncover an origin IP that a site has chosen to hide. Abuse reports belong at the abuse contact listed in the RIR record.
Checking hosting details on Bigdomainhost
If your site is hosted with Bigdomainhost, the client area (the Login link in the site menu) lists your hosting, cloud servers and invoices in one place. Web & cPanel and WordPress hosting run on LiteSpeed servers in Mumbai (BOM-1); KVM VPS and dedicated servers are in Mumbai or Delhi NCR (DEL-1). Domains using Bigdomainhost DNS point at ns1.bigdomainhost.com and ns2.bigdomainhost.com, as listed in the nameserver docs. On a VPS you can set a reverse DNS (PTR) record for your IP from the instance view, once the forward record already resolves to it. To point a domain registered elsewhere at a server, follow how to point a domain to a VPS. For help reading your own lookup results, call +91 75994 50220 during IST hours, WhatsApp the same number at any time, or email support@bigdomainhost.com.