Domain intelligence in one call: WHOIS, DNS records, SSL certificate, domain age. Essential for due diligence and security audits.
Single tool 'domain_lookup_intelligence' has a strong, detailed description (450+ chars) with clear use cases and anti-patterns (what NOT to use it for). Input schema is present with proper type and description. Output schema is documented in the description with 15 structured fields (whois, dns, ssl, domainAge). Naming follows verb_noun pattern ('domain_lookup_intelligence'). However, the tool lacks explicit parameter validation constraints (e.g., domain format regex), and the output schema is embedded in prose rather than a formal JSON Schema definition. No error handling guidance is documented. The tool is READ_ONLY, which is appropriate for this domain intelligence use case.
Use this when you need comprehensive domain intelligence -- WHOIS, DNS, and SSL data in a single call. Returns structured JSON with full domain profile. 1. whois.registrar (string) -- domain registrar name 2. whois.createdDate (string) -- domain registration date 3. whois.expiryDate (string) -- domain expiration date 4. whois.nameservers (array) -- authoritative nameservers 5. dns.a (array) -- A records (IPv4 addresses) 6. dns.aaaa (array) -- AAAA records (IPv6 addresses) 7. dns.mx (array) -- mail exchange records with priority 8. dns.txt (array) -- TXT records (SPF, verification, etc.) 9. dns.ns (array) -- NS records 10. dns.cname (array) -- CNAME aliases 11. ssl.issuer (string) -- certificate authority (Let's Encrypt, DigiCert, etc.) 12. ssl.validFrom (string) -- certificate start date 13. ssl.validTo (string) -- certificate expiry date 14. ssl.daysRemaining (number) -- days until SSL expiry 15. domainAge (number) -- domain age in days Example output: {"whois":{"registrar":"Cloudflare","createdDate":"2010-01-15","expiryDate":"2027-01-15","nameservers":["ns1.cloudflare.com"]},"dns":{"a":["104.26.10.1"],"mx":[{"priority":10,"exchange":"mx.example.com"}]},"ssl":{"issuer":"Let's Encrypt","daysRemaining":45},"domainAge":5932} Use this BEFORE domain purchases, security audits, phishing investigations, or due diligence on vendors. Essential for checking domain legitimacy, SSL health, and DNS configuration. Do NOT use for company data -- use company_enrich_from_domain instead. Do NOT use for IP geolocation -- use ip_lookup_geolocation instead. Do NOT use for website content -- use web_scrape_to_markdown instead. Do NOT use for email deliverability -- use email_audit_deliverability instead.
Output schema not formalized in JSON Schema. Currently documented only in prose description with example JSON. LLMs cannot reliably parse unstructured output descriptions.
Input parameter 'domain' lacks format constraints. No regex pattern, length limits, or validation rules documented. LLMs may pass invalid domains (spaces, special chars, etc.).
No error handling guidance. Tool description does not explain what happens on invalid domain, network timeout, or missing DNS records. LLMs have no recovery path.
Output schema example shows optional fields (e.g., dns.cname, ssl.issuer) but does not document which fields are always present vs. conditional. Agents cannot reliably extract required data.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2025-06-18+ | v2 |