What problem does it solve? Determining who actually owns and operates a domain is harder than it looks: WHOIS data is redacted, registration and operation are often different parties, and shared hosting makes IP-based attribution worthless. This Skill provides the tradecraft to attribute domains correctly using passive sources. ## Core Features & Use Cases - WHOIS and RDAP Lookups: Query registration data via RDAP and registrar WHOIS, interpret EPP status codes, redaction patterns, and transfer events. - DNS Fingerprinting: Analyze A, MX, NS, TXT, SPF, DKIM, DMARC, and CAA records to identify hosting providers, mail vendors, and SaaS tenants, with vendor fingerprint tables in the reference files. - Historical and Reverse Pivots: Use historical WHOIS, passive DNS, and reverse WHOIS to pierce privacy redaction and cluster related domains by shared infrastructure. - Use Case: A fraud team refers a suspicious domain. You pull RDAP for creation date and registrar, read DNS for mail and hosting vendors, find a pre-redaction WHOIS snapshot with a registrant email, and reverse-WHOIS it to uncover a seven-domain cluster operated by one actor. ## Quick Start Use the who-owns-this-domain skill to investigate example.com and tell me who registered it and who operates its infrastructure.