Website Technology Checker

About the Website Technology Checker

Enter a website to see what it is built with: the CMS or site builder (WordPress, Drupal, Shopify, Wix…), JavaScript frameworks and libraries (Next.js, Nuxt, Angular, jQuery…), analytics and tag managers, advertising, chat, consent and payment tools, and the CDN, hosting platform, web server and language behind it.

Every find comes with its evidence — the header, cookie name, script address or HTML attribute that gave it away — and a link to the vendor’s own documentation of that marker, so you can check each answer instead of trusting a black box. MySmartCoPilot’s server fetches the page and reads it with a streaming HTML parser; only the evidence comes back, and the matching against MySmartCoPilot’s own signature set happens in your browser.

Without a pass the result is a free preview: how many technologies were found in each category, with the first finds and their evidence. The full report, copying it and the CSV and JSON downloads unlock with a Pro pass.

Common uses

• Sizing up a competitor’s or a prospect’s stack before a pitch, migration estimate or audit.
• Checking which trackers, consent tools and third-party hosts a site loads, for a privacy review.
• Confirming that a deployment really sits behind the CDN or on the host you expect.
• Finding the plugins and theme of a WordPress site you are about to take over.
• Learning how well-known sites are built, with the source of every answer.

How detection works

The check reads what a browser receives: response headers and cookie names (never cookie values), the generator meta, the addresses of scripts, stylesheets, frames, forms and images, a few attributes frameworks put in the HTML (such as ng-version or data-sveltekit-preload-data), and the addresses that inline loader snippets fetch. Each signature names the marker it looks for and links the vendor documentation or standard that defines it — a CDN’s documented response header, a framework’s documented asset folder, the cookie list a platform publishes, the IP ranges a network publishes (matched against the addresses the site’s name resolves to in public DNS). MySmartCoPilot wrote the signature set from those sources; no third-party signature database is used.

Besides the signatures, the report shows what the site says about itself: the X-Powered-By header (and the Server header when you paste headers), the proxies in Via, the caches in Cache-Status and the generator meta, word for word — plus the WordPress plugin and theme folders the page loads files from, and any other third-party hosts no signature explains.

What it can find

• CMS and builders: WordPress (with plugin and theme folders), Drupal, Joomla!, Ghost, TYPO3, Shopify, Adobe Commerce, WooCommerce, Wix, Squarespace, Webflow, Blogger.
• Frameworks, libraries and generators: Next.js, Nuxt, SvelteKit, Astro, Angular, AngularJS, Vue.js, React, Gatsby, Docusaurus, VitePress, Hugo, Jekyll, AMP, Alpine.js, htmx, Turbo, jQuery and jQuery UI, Bootstrap, Tailwind’s browser build, Font Awesome kits and Google Fonts.
• Analytics, tags, ads and monitoring: Google Tag Manager, the Google tag, Matomo, Plausible, Fathom, Umami, Simple Analytics, Mixpanel, Segment, Amplitude, PostHog, Microsoft Clarity, Yandex Metrica, Tealium, Meta Pixel, AdSense, Google Publisher Tag, HubSpot, New Relic, Datadog and Sentry.
• Widgets, consent, security and payments: Intercom, Freshchat, Typeform, Disqus, Cookiebot, Didomi, iubenda, reCAPTCHA, hCaptcha, Stripe.js, PayPal, Razorpay, Braintree, Paddle, YouTube, Vimeo and Wistia embeds, Google Maps, Mapbox and Leaflet.
• Delivery and servers: Fastly, Amazon CloudFront, Azure Front Door, Google Cloud load balancing, Vercel, Netlify, GitHub Pages, Heroku, Render, Fly.io, App Engine, Cloud Run, jsDelivr, unpkg, Cloudinary, imgix, nginx and Apache (from pasted headers), PHP, Express, Ruby on Rails, Django, ASP.NET, Java servlet containers, HTTP/3, Brotli and HSTS.

Why something may be missing

• Server-side choices often leave no trace. Databases, languages behind a proxy and private APIs are invisible from outside unless the server names them.
• Software loaded later is not seen. The check reads the HTML as delivered and does not run scripts, so tags a tag manager adds after loading, and apps that build the page in the browser, show less.
• Sites can hide or change markers: many remove Server and X-Powered-By, and a CDN in front replaces the origin’s headers.
• Bots get different answers. A site may answer MySmartCoPilot’s server (as MySmartCoPilotBot) with an error or a bot check — the report says so; paste the source from your browser then.

Limitations

• One page per check, read up to 2 MB; other pages of the site can use other software.
• Detection depends on documented markers. A technology that leaves none in the headers or HTML is not listed, and the list of signatures is finite.
• Versions are shown only where a marker carries one (the generator meta, a versioned file name, an X-Powered-By or pasted Server header), and sites often serve old or edited version strings.
• From a URL, the site’s own Server header cannot be read: it is replaced on the way to MySmartCoPilot’s server, so web servers such as nginx or Apache appear only when you paste the response headers from your browser.
• Only public http:// and https:// sites on the standard ports can be fetched; private and internal addresses never are.
• Text is read as UTF-8; non-UTF-8 pages may show wrong characters in titles (addresses are not affected).

Privacy

Sends data online, including to MySmartCoPilot’s server

In “From a URL” mode the address goes to MySmartCoPilot’s server, which fetches the page and returns only the evidence; nothing is stored, and the log keeps only the host name, status and time. Pasted source and headers are read in your browser and never uploaded.