Many site owners do not know who hosts their WordPress site. A developer may have set it up years ago. A business partner may have paid the bills. Then something breaks, or a renewal notice arrives, and nobody can say where the site lives.<\/p>\n
The good news is that you can find out in a few minutes. This guide shows several reliable ways to identify a web host, from simple checks in your own records to lookups that work on any public site. You will also learn why some methods fail and what to do when a site hides its host.<\/p>\n
Your web host stores your site files and database and serves them to visitors. Almost every serious fix touches the host at some point. If the site goes down, you need to contact the right support team. If you want to restore a backup, you need the right control panel. If you plan to move the site, you need to know where it is leaving from.<\/p>\n
Knowing the host also helps you judge performance. A slow site on weak shared hosting needs a different fix than a slow site on a strong server. Our guide on whether shared hosting is good for WordPress<\/a> explains how plan type affects speed and stability.<\/p>\n There is a money reason too. Many owners pay for hosting without noticing. A forgotten plan may renew each year, or two plans may run side by side. Finding the host lets you check what you pay and what you get. Our overview of WordPress hosting costs in 2026<\/a> gives a fair benchmark.<\/p>\n Finally, you may want to look up the host of a site you do not own. A competitor, a client, or a site you plan to buy all raise this question. The public lookup methods in this guide work for those cases as well. They show where a site is served from, not who owns the account.<\/p>\n Three different companies often play a part in one website, and people mix them up. Keep them apart before you start, or you may chase the wrong answer.<\/p>\n The domain registrar<\/strong> is the company where you bought your domain name. It holds the registration, and it may be a different company from your host. A domain lookup, often called WHOIS, usually shows the registrar and not the host. This is the most common mistake.<\/p>\n The DNS provider<\/strong> runs the name servers. Name servers are the directory that tells browsers which server holds your site. Many hosts also run your DNS, so the name servers often point to the host. But you can move DNS to another company while the site stays where it is.<\/p>\n The web host<\/strong> is the company whose servers store and deliver your site. It is the answer you want. Some owners also place a content delivery network, or CDN, in front of the host. A CDN is a network of servers that caches your pages close to visitors. It can hide the real host from simple lookups, and a later section explains how to see past it.<\/p>\n Think of it like a shop. The registrar owns the street address, the DNS provider gives directions, and the host is the building where the shop sits.<\/p>\n If the site is yours, the fastest answer is often in your own files and inbox. Do these checks before any technical lookup.<\/p>\n Search your email for words like “hosting,” “invoice,” “renewal,” and “welcome.” Hosts send a welcome email with login details when you sign up, and they send renewal notices before each charge. Check your bank or card statement for a recurring charge that matches your site. The name on that charge is often the host.<\/p>\n Next, look inside WordPress. Go to Tools \u2192 Site Health \u2192 Info<\/strong> and open the Server<\/strong> section. It shows the web server software, the PHP version, the database version, and sometimes the server architecture. This does not always name the host. But some hosts leave clues, such as a custom server name, and the details help a support agent confirm your setup.<\/p>\n Also check your error messages. A PHP error often shows a file path, such as Finally, ask the people around you. Your developer, designer, or former employee may have the account. If you know who built the site, ask them first. A short email can save an hour of detective work.<\/p>\n A name server lookup is one of the best public methods. It reads the DNS records for your domain, and those records often name the host. You do not need to log in anywhere.<\/p>\n The company name inside those server names is usually the DNS provider. If the name matches a hosting company, that company probably hosts your site. For example, names that include a well-known host’s brand point straight to it.<\/p>\n This method fails in two cases. First, the name servers may belong to a registrar or a separate DNS service. Second, the name servers may belong to a CDN or security service. In both cases you only learn who runs DNS, not who hosts the files. Treat the result as a strong clue, and confirm it with the IP address method below.<\/p>\n These lookups only read public data. They do not change anything on your site or your domain. Do not change name servers while you investigate, because a wrong change can take your site offline and your email with it. If you ever do need to edit DNS, write down the current records first.<\/p>\n Every server has an IP address, which is a number that works like a street address. Your domain points to one. You can look up who owns that address, and the owner is often the host. This is the most reliable public method when no CDN sits in front.<\/p>\n First, find the IP address. On Windows, open Command Prompt. On macOS or Linux, open Terminal. Type The result shows one or more IP addresses. Copy the first one. Then open a free IP lookup tool and paste the address in. Look for the field named Organization<\/strong>, ISP<\/strong>, or Network name<\/strong>. That field names the company that owns the address block.<\/p>\n If the organization is a hosting company, you have your answer. If it is a large cloud platform, your host may rent space from that platform, and the final host could be a smaller company. In that case, check the name servers and your billing records to find the company you actually pay.<\/p>\n One more tip: do a reverse lookup on the IP. A reverse lookup turns the number back into a server name, and that name can include the host’s brand. Many lookup tools show it in a field called Hostname<\/strong> or Reverse DNS<\/strong>.<\/p>\n HTTP headers are small notes that a server sends with every page. Some of them reveal the server software and sometimes the host. You can read them in any modern browser without extra tools.<\/p>\n Open your site. Right-click the page and choose Inspect<\/strong>, then open the Network<\/strong> tab. Reload the page. Click the first item in the list, which is usually the page itself. Open the Headers<\/strong> section and scroll to Response Headers<\/strong>.<\/p>\n Look at fields like Headers also tell you whether a CDN is present. Fields that mention a cache, a CDN, or a proxy suggest a middle layer. When you see one, the IP address lookup may show the CDN and not the real host. Use the next section to deal with that.<\/p>\n This method works best as a second opinion. Headers differ from site to site, and owners can hide or change them. Use them alongside the name server and IP checks, not alone.<\/p>\n Sometimes every lookup points to a security or caching service. This happens when the site uses a CDN or proxy. The service answers visitors and passes requests to the real server in the background. Lookups then show the service and hide the host.<\/p>\n You still have several options. If the site is yours, log in to your CDN or DNS account and read the DNS records there. The record that points to your origin server holds the real IP address. Look it up with the IP method above. That address belongs to your host.<\/p>\n If the site is not yours, you can try a few clues. Look at older DNS records through a free DNS history tool, since the site may have used its host directly before adding the CDN. You can also check the mail server records. When email runs on the same server as the site, the mail server name may show the host.<\/p>\n If none of these work, the owner is the only reliable source. Ask them, or contact the registrar for help with your own domain. Never try to bypass security protections to uncover a host on a site you do not control.<\/p>\n Once you know your host, save the details somewhere safe. Write down the company name, the login link, the plan name, the renewal date, and the support contact. If you plan to change hosts, take a full backup first, and read our guide on how to move a WordPress site from one host to another<\/a>.<\/p>\nHost, Registrar and DNS Provider: Know the Difference<\/h2>\n
Start With Your Own Records<\/h2>\n
\/home\/username\/public_html\/wp-content\/<\/code>. The folder pattern points to a type of hosting setup, and the username may match your control panel login.<\/p>\nFind the Host With a Name Server Lookup<\/h2>\n
\n
ns1.example-host.com<\/code>.<\/li>\n<\/ol>\nFind the Host With an IP Address Lookup<\/h2>\n
nslookup yourdomain.com<\/code> and press Enter. You can also type ping yourdomain.com<\/code>. Both commands only read information. They do not change your site.<\/p>\nCheck HTTP Headers in Your Browser<\/h2>\n
server<\/code>, x-powered-by<\/code>, and any custom field that starts with x-<\/code>. A server<\/code> value tells you the web server software. That is not the host name. But some hosts add their own header, or a name in the server field, and that gives the answer away.<\/p>\nWhat to Do When a CDN or Proxy Hides the Host<\/h2>\n