domain-analyzelisted

# Domain Analysis **What this does:** builds a complete, evidence-based picture of one domain, its registration, safety, DNS setup, cross-TLD footprint, backlink profile, current usage, and market and legal context. **Data interfaces it needs.** DomainKits MCP supplies part of the technical evidence through the tools below; host-provided web search and WebFetch supply public context and page inspection. Equivalent providers are acceptable. Never assume an MCP payload contains a record type or field that it does not actually return. Mark a missing field or capability `Unavailable` and continue. - WHOIS / registration lookup, DomainKits: `whois` - DNS records (at least A, AAAA, MX, NS, TXT, CNAME; CAA when relevant), DomainKits: `dns` - Safe Browsing / malware status, DomainKits: `safety` - Backlink profile (rank, referring domains, spam score, and link-type distribution when the source provides it), DomainKits: `backlink_summary` - Cross-TLD registration data, DomainKits: `tld_check` - Public Suffix List rules and IDN / punycode conversion, for input normalization - Web search capability (market background, news, disputes) - Web fetch capability (load the domain and its variants) ## Input normalization Before analyzing, resolve the input to a single registrable domain, but do not silently change the user's intent. If the input is a URL, subdomain, or path, state the registrable domain you will analyze (for example, `https://blog.example.co.uk/x` reduces to `example.co.uk`