Martech Zone AppsMartech Zone Query Tools

Tech Stack Lookup: What Is That Website Built With?

Key Takeaways

  • Enter a domain and the lookup checks public signals in six steps: the domain registry, DNS records, IP ownership, the home page, the site’s Google Tag Manager (GTM) container, and its ads.txt files. Every finding includes the evidence behind it. Detected vendors, plugins, and platforms in the results link to their pages, and acronyms link to glossary definitions.
  • Results are grouped by registrar and domain age; hosting, DNS, and CDN providers; Email (Inbound) and Email (Outbound); Other Third-Party Services; the CMS and frameworks; detectable add-ons such as WordPress Plugins, Drupal Modules, Joomla Extensions, Magento Extensions, Shopify Apps, and BigCommerce Apps; analytics and tag management; CRM and marketing automation; and ad platforms. You can download a PDF report.
  • Use the same report in two ways. For a competitor, it shows how they ship content, capture leads, send email, and buy or sell ads. For a site you admire, it is a map of the stack behind the experience, so you can study how it was built instead of guessing.
  • A Not detected result means the tool found no public evidence, not that the site does not use that type of platform. The lookup reads the home page without running JavaScript, and a CDN can hide the origin host. Dashboard-only add-ons, add-ons that load only on other pages, and add-ons hidden by asset combining or hardening are missed.
  • Every add-ons card, including in the PDF, carries this caption: “These are active add-ons detectable from the public site, not a complete list.” Wix, Squarespace, and Webflow get a limited-visibility note, because third-party tools on those platforms usually show up in other categories when their scripts are detectable.

Curious what runs a competitor’s, prospect’s, or client’s website? Enter a domain, and this tool checks public signals in six steps: the domain registry, DNS records, IP ownership, the home page, the site’s Google Tag Manager container, and its ads.txt files. Every finding includes the evidence behind it, so you can verify it yourself.

Results are broken down by category: the domain registrar and domain age; hosting, DNS, and CDN providers; the inbound email provider; platforms authorized to send email for the domain; email authentication with SPF, DMARC, and DKIM; SaaS tools verified in DNS; the CMS and frameworks; analytics and tag management; CRM and marketing automation; and ad platforms. You can download the results as a PDF report.

Tech Stack Lookup

Website Tech Stack Lookup v1.1.3Last Update: Nov 21, 2026

Enter a domain, then click Look Up. We check public DNS, the domain registry, the home page and ads.txt, then list each provider with the evidence we found.

Required — A website domain such as example.com. A full URL works too; only the domain is used.
Was this helpful?

Sites behind a CDN hide their origin host, and some tags only load after a visitor interacts with the page. A Not detected result means we found no public evidence, not that the site doesn’t use that type of platform.

The findings are most useful when you read them with a question in mind. If you are researching a competitor, you are looking for operating clues: how they publish, how they capture demand, who sends their email, and which vendors they have already committed to. If you landed on a site you admire and want to understand how it was built, you are looking for a starting map. The report will not hand you a complete architecture diagram, but it will tell you which public systems are in play and why each one is worth a closer look.

FindingFor a CompetitorFor a Site You Admire
Registrar and domain ageHow established the property is, and who manages the domainWhether you are looking at a mature brand or a recent rebuild
Hosting, DNS, and CDNScale, performance posture, and how hard a migration would beWhether speed and resilience come from the origin, the edge, or both
Email (Inbound) and Email (Outbound)Who receives their mail, which platforms may send for the domain, and how strictly they protect itThe sending stack behind a strong newsletter or lifecycle program
Other Third-Party ServicesTools verified in DNS or found on the page that do not belong in a tighter categoryThe broader operating stack, not just the public website
CMS and frameworksHow fast they can ship content, commerce, and campaignsWhich platform produced the experience you liked
Detectable add-onsThe public plugins, modules, extensions, or apps that shape their workflowA starting list of the extras behind forms, merchandising, or analytics
Analytics, CRM, and adsHow they measure, nurture, and buy or sell mediaThe measurement and demand layer behind the pages and forms

Domain Registrar and Domain Age

The registrar is the company that manages the domain’s registration. The lookup reads the public registry record and, when the registry publishes it, the registration date, domain age, expiration date, and last change date.

For a competitor, age is a quick honesty check. A brand that feels new may be sitting on a ten-year-old domain, or a long-running company may have moved to a fresh name last quarter. That changes how you read their SEO history, their backlink profile, and any “new entrant” story they tell in the market. The registrar and expiration details also tell you something about domain hygiene. A well-run company usually keeps domains at a known registrar, such as Namecheap, and renews them well in advance. An upcoming expiration, or a recent unexplained change, can be a signal to look closer before you treat the domain as stable.

If you are studying a site because the work impressed you, age helps you set expectations. A two-month-old domain with a polished marketing site is probably a focused launch, maybe on a website builder or a fresh WordPress install. A fifteen-year-old domain with a modern front end often means a redesign on top of a long-lived property, which is a different kind of lesson. You are not just looking at a pretty page. You are looking at a property that has been maintained, migrated, or rebuilt, and the registrar record is the first clue to that timeline.

Hosting, DNS, and CDN Providers

These three findings describe the infrastructure under the site: where the origin lives, who answers DNS queries, and whether traffic is fronted by a content delivery network or security edge. The lookup identifies hosting from platform signals and, when the origin is visible, from IP ownership. DNS providers come from the domain’s name servers. The CDN and security edge come from response headers and related DNS clues.

Against a competitor, this is about scale and switching cost. A team on a managed platform can often ship changes quickly, but may be constrained by that platform’s limits. A custom origin behind Cloudflare or another edge network is usually harder to move and may be investing in performance, bot management, or a web application firewall. If two competitors share the same host or DNS vendor, you have a hint about their operating model and, sometimes, about shared agencies or preferred providers in the category. If the site sits behind a CDN, treat the edge network as the edge, not as the host. The origin can be hidden on purpose, and guessing it is not useful.

When a site feels unusually fast or unusually resilient, this is often why. The CMS may be ordinary. The difference may be a CDN cache, image handling at the edge, or a host that is tuned for that platform. If you are trying to reproduce a result you liked, start here before you copy visual details. A beautiful theme on a slow origin will not feel like the site you admired, and a simple page can feel premium when the edge is doing the heavy lifting. The DNS provider also matters more than it first appears, because email, verification records, and many third-party services are configured there. A DNS migration is an operations event, not just a website change.

Email (Inbound) and Email (Outbound)

Email is one of the richest public views into a marketing and operations stack, because so much of it has to be published in DNS to work. The lookup now splits this into two cards rather than a separate authentication section.

Email (Inbound) shows the MX provider that receives mail for the domain. Email (Outbound) lists each authorized sender with the evidence behind it, for example SendGrid: DKIM selector s1 (CNAME to sendgrid.net). DMARC is a single note line on that outbound card, for example DMARC policy p=reject (pct=100).

SPF is a DNS record that lists which servers and services may send email for the domain. DKIM is a cryptographic signature that proves a message was authorized by the domain. DMARC tells receiving inbox providers what to do when a message fails those checks, and where to send aggregate reports. Those records still matter. They simply show up as evidence and notes under Email (Outbound), next to the ESP or workspace that uses them.

For competitive research, the outbound list is often more revealing than the website itself. If a domain authorizes Klaviyo, Mailchimp, HubSpot, Salesforce, or another ESP, you know who may deliver campaigns, transactional mail, or sales sequences. That can tell you whether they run a serious lifecycle program, whether sales and marketing share a platform, and which vendors you may be up against in a pitch. The inbound provider is a different clue. Corporate mail at Google Workspace or Microsoft 365 looks different from mail that still terminates at a web host, and a security gateway in front of MX records often points to a more formal IT function.

A concrete example: on Yoast, Email (Outbound) showed Google Workspace, Postmark, Help Scout, ActiveCampaign, and Microsoft 365, with a DMARC policy of p=quarantine. That is a useful competitive snapshot. You can see a mix of workplace mail, transactional delivery, support, and marketing automation, plus a DMARC policy that is stricter than none but not yet at reject. If you are studying a company whose email program you respect, these records show you the sending foundation under that program. Copying campaign style without a comparable authentication setup is a common way to miss the result you thought you were reproducing. One limit is worth remembering: the lookup probes common DKIM selectors, so a custom selector can still exist even when it is not listed.

Other Third-Party Services

Verified SaaS is no longer its own card. Those findings now sit in Other Third-Party Services, together with other tools that do not belong in email, analytics, CRM, or advertising. Each entry includes how it was found, for example Atlassian (domain verification TXT). A script on the home page, a cookie, a response header, or a tag loaded by Google Tag Manager can also place a vendor here.

This is useful against a competitor because it surfaces systems you would otherwise miss: a help desk, a document platform, a product tool, or a security vendor that has been verified on the domain but is not loaded on the homepage. It can also confirm a vendor you already suspected from outbound email or from on-page tags. Treat a verification record as evidence of a relationship, not as a complete contract file. A TXT record can linger after a trial or after a team has stopped using the product day to day.

If you are exploring a stack because the website impressed you, these records widen the picture. The page may be running on WordPress or Webflow, while the company is also verifying tools for support, billing, or collaboration. A behavior analytics tool such as Hotjar may appear here or under analytics, depending on the signal the lookup used. That is often the difference between “nice site” and “this is how the business actually runs.” Use the how-found note to decide whether that vendor is relevant to the experience you came to study.

CMS and Frameworks

The CMS and frameworks card is the most direct answer to “what is this site built with?” The lookup looks at the home page HTML, asset URLs, meta generator tags, cookies, and headers. It can identify WordPress, Shopify, Webflow, HubSpot CMS, Drupal, Joomla, Magento (Adobe Commerce), BigCommerce, and a range of other content systems, ecommerce platforms, page builders, and JavaScript frameworks. A site can show more than one of these at once, for example WordPress with WooCommerce, or a CMS with a modern front-end framework.

For competitive intelligence, the platform explains the operating rhythm. A Shopify store, a WordPress site, and a custom framework imply different ways of adding landing pages, publishing product content, running experiments, and bringing in agencies. If a competitor just moved from a website builder to a full CMS, they are probably investing in content and SEO. If they are on a tightly packaged commerce platform, their flexibility may sit in apps and theme customization rather than in custom development. That should shape how you compare messaging velocity, not just how you compare visual design.

When you admire a site, this is the first question most people actually want answered. The typography, the navigation, and the checkout flow are easier to learn from once you know whether they came from a theme, a page builder, a hosted commerce platform, or a custom front end. Once the CMS is known, the lookup also opens an add-ons card for that platform, which is where plugins, modules, extensions, and store apps belong.

Detectable Add-ons

When the CMS is identified, the lookup adds a platform-specific add-ons card. The labels are WordPress Plugins, Drupal Modules, Joomla Extensions, Magento Extensions, Shopify Apps, and BigCommerce Apps. Every one of those cards, including in the PDF report, uses the same caption: “These are active add-ons detectable from the public site, not a complete list.”

Dashboard-only add-ons, add-ons that load only on other pages, and add-ons hidden by asset combining or hardening are missed. Only the home page is scanned, without running JavaScript.

For a competitor, a public add-on list is a practical look at how they actually run the platform: merchandising, SEO, forms, support, or analytics extras that shape their workflow. For a site you admire, it is the fastest way to turn “how did they do that?” into a learning agenda, as long as you treat the list as a starting map and verify anything you plan to act on.

WordPress Plugins

WordPress plugin detection uses plugin folder paths, including renamed content folders rather than only /wp-content/plugins/, plus generator tags and HTML comments, and a single /wp-json/ namespace request. readme.txt is checked only for slugs already found, at most 10, to confirm versions. It is never used as a blind probe of the plugins directory.

On Yoast, the WordPress Plugins card included WooCommerce, with a readme version of 10.0.5, YITH WooCommerce Affiliates 3.30.0, Address Autocomplete, and Helpful Pro. That mix tells you something a CMS label alone would not: commerce is native to the WordPress site, affiliate tracking is in the stack, and a handful of other public plugins are part of the live front end. If you are studying the site because the store or the content model impressed you, those names are a better starting point than guessing at the plugin directory. Use Yoast as the WordPress example, not a site whose plugin list you cannot verify in public.

Drupal Modules

Drupal module detection looks for paths under modules/contrib and modules/custom, plus libraries exposed in drupalSettings. Custom and contributed modules that leave those public traces can appear on the Drupal Modules card.

On Red Hat, Drupal Modules included Red Hat Page Builder, Red Hat Universal Navigation, and RHDC Analytics. For a competitor, that points to a custom publishing and navigation layer, not a stock theme with a few generic modules. If you admired the site’s information architecture or page composition, those module names are clues about how the experience was assembled, even though many backend-only Drupal modules will never show up.

Joomla Extensions

Joomla extension detection reads public paths for components, modules, and plugins. When those directories appear in the home page HTML, the Joomla Extensions card can name the extensions behind them. The same limits apply: an extension that only runs in the administrator, or only on an interior template, will not be listed.

Magento Extensions

Magento extension detection looks for Vendor_Module static paths and x-magento-init signals on the home page. That can reveal third-party modules a store has made public in its frontend assets. Core Magento modules are skipped, and the card still carries the complete-list caption. This article does not feature a Magento example, because a short public list can overstate how complete the picture is on a heavily customized commerce frontend.

Shopify Apps and BigCommerce Apps

Shopify and BigCommerce app detection matches known app script hosts on the home page. Apps that load a recognizable script can appear on the Shopify Apps or BigCommerce Apps card. Apps that only run in the admin, or that do not leave a public script, will not.

On Allbirds, Shopify Apps included Shopify Inbox and Triple Whale. For a competitor, that is a clue about on-site messaging and the analytics layer around paid acquisition. If you admired the store experience, those app names help explain what sits around the theme, without implying that every installed Shopify app is visible.

Wix, Squarespace, and Webflow

Wix, Squarespace, and Webflow get a limited-visibility note instead of a rich add-on inventory. Third-party tools on those platforms still appear in the other categories when their scripts are detectable from the page. If you are comparing a Webflow site you admire with a competitor on Wix or Squarespace, read the analytics, CRM, and other-services cards for those scripts, and do not expect a complete app list from the add-ons card.

Analytics and Tag Management

This category covers analytics platforms and tag managers found on the home page, including Google Analytics and Google Tag Manager. When a public GTM container is present, the lookup also reads that container and reports the tag templates and known vendors it contains. That matters because many marketing and advertising tags never appear as first-party script tags in the HTML. They are fired from the container.

For a competitor, the measurement layer shows what they care enough to instrument. A simple GA4 install is one thing. A GTM container loaded with conversion tags, remarketing pixels, and third-party analytics is another. The second pattern usually means they are actively testing, retargeting, or feeding a paid media program. You can also spot overlaps with your own stack, which is useful when you are trying to understand how they attribute demand or why their ads follow visitors around the web.

If you admired the site’s on-site experience, look here before you assume the magic is only in the design. A strong site often has an equally strong tagging plan: clean container usage, a primary analytics property, and a short list of vendors rather than a cluttered tag soup. The opposite is informative too. A beautiful page with a messy container can warn you not to copy the implementation blindly. Remember the lookup’s limits in this section. Some tags load only after a visitor interacts with the page, and the tool does not execute JavaScript on the page itself. A Not detected result is a statement about public evidence, not a guarantee that no analytics are present.

CRM, CDP, and Marketing Automation

When a CRM, CDP, or marketing automation platform leaves a public footprint on the home page, the lookup reports it here. That might be a HubSpot tracking script, a Salesforce-related tag, or another platform that identifies itself in the page code, cookies, or a GTM container.

This is one of the highest-value competitive findings because it points at the revenue engine, not just the website. A company running HubSpot or Salesforce on-site is usually capturing leads, personalizing content, or passing visitor activity into a sales process. That tells you how formal their funnel is, which categories of tools they have already bought, and where a conversation about switching costs should start. Combined with the Email (Outbound) list, it can also show whether marketing automation and inbox sending live in the same platform or are stitched together.

If you came to the site because the forms, the chat, or the personalization felt polished, this card helps explain the machinery behind that feeling. The impressive part may not be the form style. It may be that submissions land in a CRM with enrichment, routing, and follow-up already attached. Knowing that keeps your research honest: reproducing the experience may require a marketing platform, not just a better form tool. As with the other page-based findings, a platform that only loads on pricing, checkout, or after a click may not appear on the home page scan.

Ad Platforms

The ad platform card is built from ads.txt and app-ads.txt, the public files that list which advertising systems are authorized to sell a domain’s inventory. The lookup records the ad systems it finds, how many DIRECT and RESELLER relationships appear, and any manager accounts listed in the file. On-page advertising tags can also contribute to the broader advertising picture when they are visible on the home page or in GTM.

ads.txt is an IAB standard file that a publisher places at /ads.txt to authorize specific ad systems as sellers of its inventory. app-ads.txt does the same job for app inventory. DIRECT means the system has a direct relationship with the publisher. RESELLER means another party is authorized to sell on the publisher’s behalf.

For a competitor that monetizes with ads, this file is a map of their ad business. A short list of DIRECT partners looks very different from a long reseller chain. The first often suggests tighter control over quality and demand. The second can mean broader distribution, more complexity, and sometimes more risk of unauthorized or low-quality inventory. If you sell into that company, the authorized systems also tell you which ad platforms already have a relationship there. For a competitor that advertises rather than publishes, on-page ad tags and conversion pixels are the more relevant clue, and those may appear under advertising or in the GTM results rather than in ads.txt.

If you admired a publisher’s site, ads.txt helps you understand the monetization model under the editorial experience. A clean file with a small set of direct partners can be part of why the site feels less cluttered or more trustworthy. A crowded reseller list can explain heavy ad load, even when the design itself is strong. Use it as context for the experience, not as a verdict on the journalism or the brand.

Evidence, Limits, and the PDF Report

Every finding includes the evidence behind it: a registry field, a DNS record, a header, a script URL, a generator tag, a GTM container, a line from ads.txt, or, for add-ons, a path, comment, namespace, or readme confirmation. Results now link detected vendors, plugins, and platforms to their pages, and acronyms to glossary definitions, so you can go from a label to the product or the term without leaving the report. Before you brief a teammate, brief a client, or decide to evaluate a vendor, open the evidence and confirm that the match still means what you think it means.

The PDF report is there so you can keep that snapshot. Stacks change. A competitor can move hosts, swap email vendors, or redesign on a new CMS. A site you want to learn from can look different next month. Downloading the report lets you share a point-in-time view in a meeting, attach it to a prospect record, or compare two later lookups without relying on memory. Add-on cards in the PDF use the same caption as the on-page results: “These are active add-ons detectable from the public site, not a complete list.”

Read the gaps as carefully as the matches. The lookup checks public signals. It does not log in, it does not inventory a private admin screen, and it does not execute JavaScript on the page, so some tags and client-rendered tools will not appear. It focuses on the home page, plus the public GTM container and ads.txt files, so an interior checkout flow or a logged-in app can hide systems that matter. A CDN can hide the origin host. A Not detected result means there was no public evidence in those sources, not that the platform is absent. Used with those limits in mind, the report is still one of the fastest ways to understand what a website is built with, and why those choices matter.

Enter a domain in the lookup above and work through the evidence for each finding. Download the PDF when you want to share the snapshot with a teammate or save it for a later comparison.

Frequently Asked Questions

Does a Not Detected Result Mean the Site Does Not Use That Platform?

No. Not detected means the lookup found no public evidence in the sources it checks. The site may still use that type of platform in a way that is not exposed on the home page, in DNS, in a public Google Tag Manager container, or in ads.txt. Treat it as an absence of evidence, not as proof of absence.

Why Is the Origin Host Sometimes Missing?

When a site sits behind a CDN or security edge, the addresses you resolve are often the edge network, not the origin server. In that case the lookup reports the edge and does not guess the hidden host. Platform clues can still identify some hosts, but a blank hosting card is common and expected on well-fronted sites.

Can the Lookup List Every Plugin, Module, Extension, or App?

No. The add-ons card lists active add-ons detectable from the public site, not a complete inventory. Dashboard-only add-ons, add-ons that load only on other pages, and add-ons hidden by asset combining or hardening are missed. Only the home page is scanned, without running JavaScript. WordPress readme.txt files are checked only for slugs already found, at most 10, to confirm versions.

What Is the Difference Between Email (Inbound) and Email (Outbound)?

Email (Inbound) shows the MX provider that receives mail for the domain. Email (Outbound) lists each authorized sender with its evidence, such as an SPF include or a DKIM selector CNAME, and adds a single DMARC note line such as DMARC policy p=reject (pct=100). There is no separate email authentication card.

Where Did Verified SaaS Go?

Those entries now sit in Other Third-Party Services, with a short note on how each was found, for example Atlassian (domain verification TXT). Tools found on the home page, in headers, or through Google Tag Manager can appear in the same card when they do not belong in a tighter category.

Does the Tool Run JavaScript or Scan Every Page?

No. The page scan reads the home page without executing JavaScript. It also checks the domain registry, DNS records, IP ownership, a public Google Tag Manager container when one is present, and ads.txt or app-ads.txt. For WordPress, it makes one /wp-json/ request and may fetch readme.txt only for slugs already found. Tags, tools, or add-ons that load only after a click, or only on an interior page, can be missed.

What Is ads.txt, and Why Should Marketers Care?

ads.txt is a public IAB file that lists which advertising systems are authorized to sell a domain’s inventory. It helps you see how a publisher monetizes, which partners they trust, and whether relationships are direct or reseller. Advertisers and publishers both use it to reduce unauthorized selling and to understand the ad stack behind a site.

How Should I Use the Evidence Attached to Each Finding?

Read the evidence before you act on the label. A match might come from a DNS include, a verification record, a script URL, a header, a path, or a line in ads.txt, and those sources do not all carry the same weight. Results also link detected vendors, plugins, and platforms to their pages, and acronyms to glossary definitions. Confirm anything you plan to use in a competitive brief, a prospect conversation, or a build decision, and save the PDF if you need a point-in-time snapshot.

Related Articles