Free tool

See any company's GTM tech stack

Enter a website to see the CRM, marketing automation, ad pixels, intent and ABM tools it runs, then what that stack tells you: a summary, scores and insights. We read the homepage, its tag manager containers and its email DNS, and show the evidence behind every tool.

  • 6.1k+ technologies recognised
  • Reads Tag Manager and DNS
  • Nothing you look up is stored

Where the evidence comes from

Most lookup tools only read a page's source. GTM teams load half their stack through Tag Manager and send email through their CRM, so we check four places and list what matched for each tool.

Website code

Scripts, forms and widgets on the homepage, such as HubSpot forms or a Qualified chat.

Tag manager containers

The tags inside each Google Tag Manager, Adobe Launch or Tealium container the site loads: pixels like LinkedIn Insight or 6sense that never appear in the page source.

Email DNS

SPF, MX and DMARC records show the CRM and marketing platforms allowed to send as the domain, and who runs its inbox.

Verified apps

Domain verification records left by business apps such as Atlassian, DocuSign or Zoom.

GTM tools we check in depth

These have their own signatures across page code, tag manager containers and DNS. Around 6,000 more website technologies (platforms, libraries, security, hosting) come from the open-source fingerprint set.

CategoryTools
CRMHubSpot, Salesforce, Pipedrive, Zoho, Microsoft Dynamics 365, Freshworks
Marketing automation & emailAdobe Marketo Engage, Salesforce Account Engagement (Pardot), Oracle Eloqua, ActiveCampaign, Mailchimp, Klaviyo, Brevo, Customer.io, Braze
Intent, ABM & attribution6sense, TechTarget, Demandbase, Clearbit (Breeze Intelligence), ZoomInfo WebSights, Dealfront (Leadfeeder), RB2B, Warmly, Koala, Common Room, HockeyStack, Dreamdata, Factors.ai
Ad pixels & conversion tagsGoogle Ads, Meta Pixel, LinkedIn Insight Tag, Microsoft Advertising UET, TikTok Pixel, X (Twitter) Pixel, Reddit Pixel, Quora Pixel, Pinterest Tag, StackAdapt, AdRoll, Criteo
Analytics, tags & dataGoogle Tag Manager, Google Analytics 4, Adobe Analytics / Launch, Segment, Mixpanel, Amplitude, Heap, PostHog, Hotjar, Microsoft Clarity, FullStory, Plausible, Adobe Audience Manager
Chat & supportIntercom, Zendesk, Drift (Salesloft), Qualified, Crisp, LiveChat, Tidio
Meeting schedulingChili Piper, Calendly, RevenueHero
Interactive demos & videoNavattic, Storylane, Arcade, Wistia, Vidyard
Testing & personalisationOptimizely, VWO, Mutiny, Adobe Target
Email sendingSendGrid, Mailgun, Amazon SES, Postmark, Mailjet, Mandrill (Mailchimp Transactional)
Cookie consentHubSpot Cookie Banner, OneTrust, Cookiebot, CookieYes, Usercentrics, Osano, Didomi

Use it for account research before outreach, competitor teardowns, or to check what your own site really loads. Then compare options in the tool guide. Missing a tool? Tell us and we'll add its signature.

Website technology fingerprints: projectdiscovery/wappalyzergo (MIT licence), based on the open-source Wappalyzer dataset. Logos belong to their owners and identify each product.

For vendors and site owners

Wrong or outdated result? Send the domain and what should change, and we'll fix the signature. Vendors: if your logo or product name is shown wrongly, or you'd like it removed, tell us. Site owners: to stop your site being looked up at all, email us from an address at your domain and we'll add it to our opt-out list, usually within two working days. You can also block our crawler in robots.txt with User-agent: PPCBlogPro-StackLookup and Disallow: /.

Contact: hokhanhdien@gmail.com

Questions

How is this different from Wappalyzer or BuiltWith?

Those read what a page loads. This lookup also opens the site's tag manager containers and its email DNS, which is where most go-to-market tools live, and then explains the stack: a summary, scores for paid acquisition, measurement, ABM, conversion, privacy and email trust, and insights you can act on. Tools that only appear after a visitor accepts cookies or logs in need a full browser, so a browser extension can still see a few more.

How does the lookup find tools that aren't in the page source?

Many teams load their marketing tags through Google Tag Manager, so the HTML only shows one GTM snippet. The lookup also reads the tag configuration of each GTM container the page loads, and it checks DNS: an SPF record that includes mktomail.com means Marketo is allowed to send email as that domain, for example.

Why is a tool I know they use missing?

The lookup only sees public signals. Tools used server-side, inside an app behind a login, on another page, or loaded after a cookie consent choice may leave no trace on the homepage or in DNS. Absence of a tool is not proof they don't use it.

Can a result be wrong?

Every tool is listed with the evidence that matched, so you can judge it. Signals can outlive a tool: an old SPF include or a leftover tag in a GTM container can show a tool a team has stopped paying for.

Is it legal and private?

The lookup reads the same public homepage and DNS records any browser or mail server sees, identifies itself as PPCBlogPro-StackLookup, and respects robots.txt: if a site disallows crawlers on its homepage, only public DNS is read. We don't store the domains you look up beyond a one-day cache of the result, and we don't log who asked. Site owners can opt out entirely.