Finding the source of a website document means tracing where the files live on the internet and who controls them
When you load a webpage, your browser downloads files from a server somewhere. Those files have a real location — a domain name, an IP address, a hosting company. Finding the source tells you who owns the site, where it's physically hosted, and sometimes reveals whether a site is what it claims to be. You can do this with free tools built into your browser and public databases that anyone can search.
The fastest route depends on what you're looking for. If you want to know who registered a domain name, use a WHOIS lookup. If you want to see the actual code and files that make up a page, use your browser's developer tools. If you want to know which company hosts the site, check the IP address. Each method answers a different question about where a document comes from.
Key Takeaways
- Your browser's developer tools (right-click, then Inspect or Inspect Element) show you the HTML, CSS, and JavaScript that make up any webpage you visit.
- A WHOIS lookup at sites like ICANN Lookup or Whois.com reveals who registered a domain name and when, though many registrants hide their information.
- The Network tab in developer tools shows you every file your browser downloads and where it comes from — including images, scripts, and stylesheets hosted on other domains.
- An IP lookup tool tells you which hosting company owns the server that serves a website, which can reveal whether a site is hosted where it claims to be.
- DNS records (checked via nslookup or online DNS checkers) show the technical routing that points a domain name to its actual server.
Using Your Browser's Developer Tools to See Page Source
Every browser has built-in tools that let you see the raw code of any webpage. On Windows or Linux, right-click anywhere on the page and select Inspect or Inspect Element. On Mac, right-click and select Inspect Element, or use the keyboard shortcut Command+Option+I. This opens the developer tools panel, usually at the bottom or side of your screen.
The first tab you see is usually Elements (in Chrome and Edge) or Inspector (in Firefox). This shows you the HTML — the actual code that structures the page. You can expand and collapse sections to see how the page is organized. Scroll through the code and you'll see where text comes from, what images are embedded, and what links point where. This is the source code of the document itself.
The HTML you see here is what your browser received from the server. If you want to save it, right-click in the code panel and select Copy, or use Ctrl+A to select all and copy it into a text editor. Some browsers also let you right-click the page itself and choose Save Page As to download the HTML file and its linked resources to your computer.
Checking Where Files Are Actually Hosted Using the Network Tab
The Network tab shows you every single file your browser downloads when you load a page — and where each file comes from. Open developer tools, click the Network tab, then reload the page. You'll see a list of requests: HTML files, images, scripts, stylesheets, fonts, and more. Each row shows the filename, the domain it came from, the file size, and how long it took to download.
This matters because a website might display images or run scripts from other domains. For example, a news site might load ads from an advertising network, or embed a video player from YouTube. The Network tab shows you all of that. Click any request to see more details: the full URL, the response headers (which tell you about the server), and sometimes the actual content of the file.
Look at the Domain column to see which servers are being used. If a site claims to be independent but you see most requests going to a large tech company's servers, that tells you something about where the site actually lives. This is especially useful for understanding whether a site is self-hosted or relies on third-party services.
Using WHOIS Lookup to Find Domain Registration Details
A WHOIS lookup tells you who registered a domain name, when they registered it, and when it expires. Go to ICANN Lookup (icannwiki.org) or Whois.com and type in the domain name — for example, example.com. The results show the registrar (the company where the domain was bought), the registration date, and the registrant's contact information.
Many domain owners use privacy protection, which hides their real name and address behind a proxy service. If you see "Privacy Protection Enabled" or a registrar's address instead of a person's name, the owner chose to stay anonymous. This doesn't mean the site is suspicious — many legitimate businesses and individuals use privacy protection for safety. But it does mean you can't easily find out who owns the domain.
The WHOIS record also shows the nameservers — the servers that handle the domain's DNS routing. These nameservers point the domain name to the actual web server. If a domain uses unusual or suspicious nameservers, or if the registration details don't match what the site claims, that's worth investigating further.
Finding the Hosting Company Using IP Address Lookup
Every website lives on a server with an IP address — a unique number like 192.0.2.1. Finding that IP address tells you which company hosts the site. Open developer tools, go to the Network tab, reload the page, and click on the first HTML request (usually the page name itself). In the details panel, look for the Remote Address field. That's the IP address of the server.
Once you have the IP address, paste it into an IP lookup tool like IP Whois Lookup (ipwhois.io) or MaxMind GeoIP (maxmind.com). The results show you which company owns that IP address, where the server is physically located (country and sometimes city), and sometimes what type of hosting it is. This tells you whether a site is hosted by a major provider like Amazon Web Services, a smaller hosting company, or the site owner's own infrastructure.
If a site claims to be hosted in one country but the IP address shows it's actually in another, that's useful information. If a site claims to be independent but uses IP addresses owned by a large corporation, that reveals the real relationship. IP lookups are public information — anyone can do them.
Reading DNS Records to Understand Domain Routing
DNS records are the instructions that tell the internet where to send traffic when someone types a domain name. You can view these records using online DNS checkers like MXToolbox (mxtoolbox.com) or DNS Checker (dnschecker.org). Type in the domain name and select A Record to see which IP address the domain points to.
The A Record is the main one — it's the IP address of the web server. But there are other records too: CNAME records (which point to other domains), MX records (which handle email), and TXT records (which can contain verification information). Looking at all of these together tells you how a domain is set up and what services it uses.
If a domain's A Record points to a different IP address than what you found in the Network tab, something is wrong — either the DNS hasn't updated yet, or there's a mismatch. This is rare but worth checking if you're trying to verify that a site is what it claims to be.
Understanding What You Find and What It Means
Finding the source of a website document gives you facts, but those facts need context. A site hosted on a shared server with thousands of other sites is normal — most small websites work this way. A site using a privacy-protected domain registration is also normal. A site loading resources from multiple domains is normal too, because modern sites use content delivery networks and third-party services.
What matters is whether what you find matches what the site claims. If a site says it's independent but uses infrastructure owned by a corporation, that's worth knowing. If a domain was registered yesterday but claims to be an established business, that's a red flag. If the hosting location doesn't match the site's stated location, that might matter depending on what you're using the site for.
The tools themselves are neutral — they just show you information that's already public. Using them doesn't harm anything and doesn't require special permissions. The information you find is the same information that security researchers, journalists, and anyone else with curiosity can find.
Frequently Asked Questions
Can I see the source code of a website even if it's protected or minified?
Yes. Even if the code is minified (compressed into a single line to make it smaller), you can still see it in the developer tools. Minified code is harder for humans to read, but it's still the actual code running on the page. Some sites use obfuscation to make code harder to understand, but you can still view it — you just can't easily modify how it works in your browser.
Does looking at a website's source code or using these tools get me in trouble?
No. Using your browser's built-in developer tools, WHOIS lookups, and IP address checkers are all legal and normal. You're not accessing anything private or breaking into anything — you're just looking at information that's publicly available. Websites expect people to use these tools.
What if a WHOIS lookup shows a registrar's address instead of the actual owner?
The owner used privacy protection, which is a service offered by most domain registrars. It hides the registrant's real name and address. You can sometimes contact the owner through the registrar's privacy proxy, or look for contact information on the website itself. Some registrars will forward messages to the real owner if you ask.
Why would a website use multiple hosting providers or domains?
Large sites often use content delivery networks (CDNs) to serve images and videos from servers closer to users, which makes pages load faster. They might use separate domains for analytics, ads, or third-party services. This is standard practice and doesn't mean anything is wrong — it just means the site is using multiple services to function.
Can I find out who actually owns a website if they're using privacy protection?
Not easily through WHOIS alone. You can look for contact information on the website itself, check social media accounts linked to the site, or search for the domain name in news articles or business databases. Some sites are required to disclose ownership (like financial services), but most private websites can stay anonymous if they use privacy protection.