seo-recon

SEO Recon — Domain, Hosting, Stack, and Cache Reconnaissance

External domain and infrastructure reconnaissance covers what an sf-analyzer crawl does not provide: the registrar and domain age, where the server is hosted and on which ASN, which CDN sits in front of the site and whether its cache actually works, which CMS/framework the site is built with, and how traffic is measured.

These are no longer manual Bash steps, but three tools in the seohead toolkit (CLI + MCP + HTTP). Each returns ready-to-use JSON with a findings block containing plain-language conclusions. In MCP, they are seo_domain_profile, seo_cdn_check, and seo_tech_detect.

When to Use It

• "what hosting provider does the site use," "where is the server," "which ASN / provider hosts it";
• "does it use Cloudflare," "which CDN," "does caching work," "why is it slow";
• "which CMS," "which site engine," "what is the site built with," "how is traffic measured," stack detection;
• "domain whois," "domain age," "when was it registered," "who is the registrar," TLS/expiration;
• a quick competitor profile before a crawl audit.

Workflow (All Three Tools by Default)

1. Domain profile. Registration, DNS, hosting, ASN, location, and TLS in one call:

seohead domain-profile --domain example.com

The response contains: registration (registrar, age_years, expires_in_days, statuses), dns (A/AAAA/NS/MX/TXT, dns_provider, mail_provider, spf, dmarc), hosting (ip, asn, as_name, network, country, reverse_dns), tls (issuer, expires, days_left), and flags — risks summarized in one line. Registration data comes from RDAP; for ccTLDs without RDAP (.by and some .ru domains), the tool automatically falls back to the system whois command. If it is unavailable, the tool honestly marks source: none instead of inventing data.

2. CDN and cache. Not whether caching is configured on paper, but whether it works:

seohead cdn-check --url https://example.com

The tool makes three requests: an initial request, a repeat request (to catch MISS → HIT), and a conditional request (to check for 304). The response contains: cdn, transport (HTTP version — the http_version_measurable field honestly states when it cannot be measured without the h2 package; HTTP/3 in Alt-Svc, brotli/gzip, and the TTFB of the first and second requests), and cache (parsed cache_control, etag/last_modified, hit_first/hit_second, warmed_up, and revalidation).