To learn how to tell what software a website is built with, you need to check its front end code and server headers. You can use automated browser extensions to scan the site instantly. If that fails, you must inspect the source code manually to find specific file paths and meta tags.
Knowing how to tell what software a website is built with helps you reverse engineer a competitor or audit a client site. Sometimes a quick scan gives you the whole picture. Other times, the site owner hides their technology stack behind a proxy. You have to know exactly where to look to uncover the truth.
Use Automated Lookup Tools First
Start with the fastest method available. Automated tools scan the public footprint of a webpage and cross reference it against a database of known software signatures. They look at cookies, JavaScript variables and file paths to identify the platform.
Before installing anything on your computer, try a web based scanner. You can paste the address into a free website platform checker to see the content management system and the front end framework immediately. This tells you if the site runs on standard software like WordPress or Shopify without needing any browser extensions.
If you do this research often, you should install a browser extension. Wappalyzer is the industry standard for this task. You install it in Chrome or Firefox. When you load a webpage, the extension icon lights up. Click it to see a list of the software running on that page. It categorises the technology stack into analytics, payment processors, content management systems and web servers.
Another excellent option is BuiltWith. BuiltWith maintains a massive database of website technology trends. Their browser extension works similarly to Wappalyzer. However, their main website offers a deeper historical lookup. If you search a domain on BuiltWith, you can see what software the website used in the past. This historical data helps if a site recently migrated to a new platform.
These tools are incredibly powerful. They save you hours of manual code inspection. They instantly highlight the ecommerce platform, the analytics tools and the marketing widgets. However, they are not perfect. They rely on known signatures. If a developer customises the code heavily, the automated tools will miss the underlying framework.
Inspect The Source Code Manually
Automated tools miss things. Sometimes they cache old results. When you need to be certain, you must look at the code yourself.
Open the website in your browser. Right click anywhere on the page and select the option to view the page source. This opens the raw HTML document. You are looking for specific footprints that reveal the underlying software.
Search the document for a generator meta tag. Many platforms inject a specific line of code into the head section of the HTML to announce their presence. Press the search shortcut on your keyboard and type the word generator. You might see a line that names WordPress or Webflow directly. If you see this, you know exactly what software built the site.
Next, look at the file paths for images and scripts. Different platforms store their assets in highly specific folder structures. Search the source code for these common paths.
- Type wp-content to check for WordPress.
- Type wp-includes to verify the core WordPress installation files.
- Type cdn.shopify.com to identify a Shopify store.
- Type _next to see if the site uses the Next.js framework.
- Type assets.squarespace.com to spot a Squarespace site.
- Type static.wixstatic.com to confirm a Wix website.
- Type ghost.org to spot a Ghost blogging platform setup.
If you find these paths, you have your answer. The platform cannot function without loading these core files. The developers cannot easily hide these asset URLs without breaking the website.
You should also look for specific class names in the HTML body. WordPress often uses a class called wp-block for its content elements. Type elementor to see if they use the popular WordPress page builder. Webflow uses a class called w-node for its grid layouts. These structural clues tell you exactly how the page was assembled.
Check The Network Headers
The server sends hidden information every time your browser requests a webpage. These HTTP response headers often declare the exact software running on the server.
To view these headers, right click the page and select the inspect option to open your browser developer tools. Click the network tab. Refresh the page. You will see a long list of files loading in real time. Scroll to the very top of that list and click the first item. This is the main document request.
Look at the panel on the right. Find the section labelled response headers. You are looking for two specific lines.
The first is the server header. This tells you the web server software. You might see nginx or Apache. Sometimes it reveals more, like cloudflare or fastly.
The second is the powered by header. Backend frameworks use this to announce themselves. You might see PHP or Express. If you see Express, the site is running on a Node.js backend. If you see ASP.NET, the server is running on a Microsoft Windows environment. This distinction is critical because it dictates what kind of developers you need to hire if you want to modify the system.
Checking headers is vital when you audit a site before a migration. If you plan to rebuild the site, you need to know what the current server runs. You can review our standard setup costs to compare different hosting stacks. Understanding the current infrastructure helps you plan the technical requirements for the new build.
Map The Third Party Scripts
A modern website is rarely built with just one piece of software. It relies on a stack of third party tools to handle analytics, customer support and marketing.
You can find these tools by inspecting the JavaScript files loading in the network tab. Filter the network requests by the JS option. Look at the domain names hosting these scripts.
You will frequently see tracking codes. Google Tag Manager and Facebook scripts load from their respective domains. You will also find advertising pixels. Look for TikTok, LinkedIn and Pinterest tracking codes. If a business loads all of these pixels on their homepage, they are running multi channel advertising campaigns. This tells you exactly where they spend their marketing budget.
You will also spot customer service widgets. If a site uses Intercom or Zendesk, you will see their scripts loading in the background.
This script analysis tells you how the business operates. If you see advanced marketing automation scripts, you know they invest heavily in lead generation. If you are looking at a competitor, this shows you exactly what tools they use to convert their traffic.
You can also spot performance issues here. Many sites load ten different tracking scripts that slow down the page. If you see a massive list of external JavaScript files, the site is likely suffering from bloat. We often review these bloated setups during our initial audits. You can see examples of our technical audits to understand how we clean up these messy configurations.
Check DNS And Hosting Records
The website code only tells you half the story. To find out where the website lives, you need to check the domain name system records.
You can use a free online DNS lookup tool to check the A record of the domain. The A record points to the IP address of the server. Once you have the IP address, you can run an IP lookup to find the hosting provider. This tells you if the site runs on Amazon Web Services, DigitalOcean or a standard shared host like Bluehost.
You should also check the MX records. The mail exchange records tell you what software the company uses for their email. If the MX records point to Google, they use Google Workspace. If they point to Outlook, they use Microsoft 365.
You can also check the TXT records. Businesses use TXT records to verify their domain ownership with third party services. You will often see verification strings for Google Search Console, Facebook Business Manager and Apple Pay. These records confirm which external platforms are connected to the business operations.
Checking the nameservers gives you another clue. If the nameservers point to Cloudflare, you know the site uses their proxy service. If the nameservers point to Shopify, you know the domain is managed directly through the Shopify platform.
These infrastructure clues help you build a complete profile of the business. You can see exactly how much technical control they have over their environment.
Why Some Software Stays Hidden
You will encounter websites that give you absolutely nothing. The automated tools show blank results. The source code lacks generator tags. The network headers show generic information.
This happens for three specific reasons.
First, the site sits behind a reverse proxy or a content delivery network. Services like Cloudflare intercept the traffic before it hits the origin server. When you check the headers, you only see the proxy software. The real server software remains hidden from the public internet.
Second, the developers use a headless architecture. A headless setup separates the back end content management system from the front end website. The business might write their articles in a traditional system, but the website you see is a static application. The browser never touches the back end directly. Client side inspection tools cannot see the headless system because it never loads in the browser.
Third, the site owner actively strips the identifying marks. Security teams often remove the server headers. They delete generator meta tags. They do this to stop automated bots from scanning their site for known software vulnerabilities. If a hacker cannot tell what software a website is built with, they have a harder time exploiting it.
Put The Clues Together
No single method gives you the complete picture every time. You have to combine the clues to form a conclusion.
Start with the browser extensions to grab the obvious front end frameworks and analytics tools. Move to the source code to check the file paths for the core platform. Finish with the network headers and DNS records to identify the server environment.
When you find conflicting information, trust the network headers and the file paths over the automated tools. A site might leave an old plugin active while running entirely on a new platform, confusing the automated scanners. The raw code never lies.
If you still cannot figure it out, the site is likely a custom build. Small businesses usually stick to off the shelf platforms. Large enterprises build custom software from scratch. If you see no platform footprints, no standard file paths and heavily obfuscated code, you are looking at a bespoke application.
If their current stack is a total mess of conflicting scripts and hidden servers, they probably need a complete overhaul. We often rip out these bloated setups when we transition a client, rebuilding the entire foundation as a fast, clean local business website.
You can always reach out to us if you need help auditing a complex technology stack. We map out these systems every day to figure out exactly how they work.