Public URL check
What is this website built with?
Find out what a website is built with: CMS, tech stack and analytics
CMS, builder and platform
The check looks for WordPress, Bitrix, Tilda, Webflow, Shopify, Wix, Joomla, Drupal, Magento, WooCommerce and similar platform hints in HTML, file paths and meta generator.
Frameworks and libraries
URLCompass analyzes public scripts and markup for Next.js, Nuxt, React, Vue, Angular, Svelte, jQuery, Bootstrap, Tailwind and other frontend signals.
Analytics, pixels and marketing
The report highlights Google Tag Manager, Google Analytics, Yandex Metrica, Meta Pixel, TikTok Pixel and other visible tracking or marketing scripts.
Server, CDN and headers
The check reads Server, X-Powered-By, Cloudflare/CDN hints, Content-Type, HTTPS, robots.txt and sitemap.xml for infrastructure context.
Example result
What the report can show before you open it
The exact values depend on the URL, but the report highlights practical signals instead of a raw technical dump.
CMS, builders, frameworks, analytics, pixels, CDN and asset hosts.
External script and stylesheet hosts reveal CDN, analytics, widgets and libraries.
HSTS, CSP, X-Frame-Options, X-Content-Type-Options and Referrer-Policy.
The report groups output into critical issues, recommended fixes and useful context.
Report sections
The scan keeps the result readable
Platform
CMS, builder, ecommerce engine and page generator hints.
Frontend
JavaScript frameworks, libraries, CSS frameworks and public asset hosts.
Marketing
Analytics counters, pixels, tag managers and marketing scripts.
Infrastructure
Server headers, CDN, IP, HTTPS, robots.txt and sitemap.xml.
FAQ
Common questions
Does URLCompass need access to the website admin area?
No. The report is built from public signals available by URL: HTML, headers, DNS, TLS, robots.txt and sitemap.xml.
Can it show exact traffic or private analytics?
No. Exact traffic requires analytics access or paid data sources. URLCompass intentionally separates public checks from private metrics.
What should I do after the report?
Start with failed checks and warnings: indexability, HTTPS/TLS, security headers, page speed, missing metadata and weak DNS/mail protection.
Which URLs can be checked?
Use public http or https pages. Localhost, private IP addresses and closed admin pages are blocked to keep the checker safe.