Hosting & CMS Architecture Detector
Check a public domain for obvious hosting and application signals so you can see whether the site looks like WordPress, Laravel or a static build, and whether the infrastructure shows signs of a standalone VPS or managed platform.
This is a practical first-pass detector for agency handovers, inherited websites and migration planning where nobody is fully sure what stack is actually running.
It uses public DNS, response headers and visible endpoint signals only. It is meant to reduce guesswork quickly, not to replace a full infrastructure review when the site is fragile or business-critical.
Run the detection
Enter a public domain. The detector checks response headers, public WordPress endpoints and obvious hosting or framework signals.
What this check does
- Fetches the public homepage and inspects visible response headers.
- Checks for obvious WordPress signals such as a live `/wp-json` endpoint or asset markers.
- Looks for common Laravel, Next.js or static-build fingerprints in public markup or cookies.
- Uses public signals only and blocks private-network targets.
Important limits
- It can only see public headers, endpoints and visible front-end signals.
- Cloudflare, reverse proxies and managed platforms often hide the true origin host.
- It does not log into admin panels or inspect private deployment settings.
- For migration planning or stack cleanup, a deeper infrastructure review is still the safer next step.
Need the webhook path fixed properly?
If the stack looks inherited or unclear, the safer path is to review the actual hosting path, CMS state, admin ownership and migration risk directly instead of inferring too much from public fingerprints alone.
Practical support for VPS, hosting, domains, DNS, email routing, SSL, migrations and unclear access or responsibility.
Direct help for broken forms, failed deployments, unstable pages, integration issues and inherited website setups.