The Proxy Signal
The DNS lookup — the first thing that happens when you visit any website — contains a hidden signal about the entire technology stack behind it. If the DNS resolves through Netlify or Vercel, the site almost certainly runs a modern Jamstack framework. If it resolves through GoDaddy, Bluehost, or Hostinger, it almost certainly runs WordPress on shared hosting. The DNS provider predicts the framework with surprising accuracy.
The Detection Dimension
WebPulse detects frameworks by analyzing HTML signatures — meta tags, script paths, header patterns. But DNS adds a detection dimension that works before the page even loads. A DNS-first detection pass could pre-classify sites with high confidence: Netlify DNS = modern, shared hosting DNS = WordPress, AWS Route53 = enterprise custom. The HTML analysis then confirms or corrects the DNS-based prediction.
This isn't theoretical. Hosting providers are framework-specific by design. Netlify was built for static sites. Vercel was built for Next.js. WP Engine was built for WordPress. The hosting choice is the framework choice — and the DNS record is the hosting choice made visible.
Why This Matters
If DNS predicts framework, then DNS data is framework intelligence. The total number of domains on Netlify DNS approximates the total number of Jamstack sites. The total number of domains on shared hosting approximates the total number of WordPress sites. This is a new data source — faster than HTML analysis, available at massive scale, and hiding in plain sight in every DNS query. The infrastructure layer below the framework IS the framework signal.
