detectech by Osman

🔍 Discover the hidden tech stack behind any website. Advanced technology detection for developers, designers, and tech enthusiasts.

1 User

Rated 5 by 1 reviewer

Support this developer

The developer of this extension asks that you help support its continued development by making a small contribution.

Release notes for 1.3

What’s New

Backend detection: Smarter Next.js API recognition (/api, /
trpc, /graphql) with a clear “Next.js (runtime)” fallback when no
API calls are seen. Stronger PHP (PHPSID, .php endpoints, WordPress
admin-ajax/wp-json), ASP.NET (__RequestVerificationToken, .AspNetCore,
ASP.NET_SessionId, .aspx/__VIEWSTATE), Laravel (csrf-token,
laravel_session, remember_web, window.Laravel/laravel-mix), and Express/
Fastify/NestJS via response headers.
Database signals: Improved Supabase detection (domains, /rest|/
auth|/realtime, localStorage, WebSocket), with PostgreSQL inferred when
Supabase is present. Broader Firebase coverage (firebaseio, gstatic
firebasejs, Firestore/Identity Toolkit endpoints, initializeApp,
localStorage prefixes, IndexedDB names).
Hosting accuracy: Vercel now detected via headers (x-vercel-id/
cache/server), plus Netlify (x-nf-request-id), Cloudflare (cf-ray),
AWS CloudFront, and Azure App Service (azurewebsites.net, ARRAffinity).
Items show a [via headers] badge when applicable.
UI improvements: Cleaner badges that indicate [via inferred] and [via
headers], with localized English/Turkish text and informative tooltips.
Developer experience: Makefile targets to package for Chrome (MV3) and
Firefox (MV2), updated contributor guide (AGENTS.md), and dist/ outputs
ignored by default.
Privacy & performance: All detection runs client‑side. No new
permissions; no data leaves your browser. Header checks are same‑origin
and lightweight.

Notes

Some backends/databases only visible when client-side signals exist
(e.g., API calls or SDK usage). Server‑only setups may not expose a
detectable footprint.