Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →avizmarlon/dns-and-whois-tools
DNS lookup, WHOIS, passive-DNS history, IP reputation, and subdomain enumeration procedures. Auto-load when nslookup / dig / whois / host is mentioned, when investigating DNS records (A, NS, MX, CNAME, TXT), when researching historical nameservers, when checking IP reputation (AbuseIPDB, ipinfo.io), when enumerating subdomains (HackerTarget, crt.sh, SecurityTrails), or when reasoning about registrar vs hosting provider.
Passed 23 of 24 test cases with the skill, and 15 of 24 without it.
and 14 more in the full report
8 fixed15 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When investigating historical nameservers for migrated-app.net, SecurityTrails returned no results. Which service should be queried next in the fallback chain before contacting customer support or domain owners?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends WhoisFreaks as the next fall-through option after SecurityTrails | Missed | Passed |
| Lists ViewDNS.info as the option following WhoisFreaks in the fallback chain | Missed | Passed |
The instructions your model reads when the skill loads.
Investigation toolkit for DNS, WHOIS, IP reputation, and passive-DNS work. Applies to any domain or IP across public internet domains.
wsl dig — fullest output, supports +short, +noall +answer, ANY, AXFR, etc.curl -s "https://dns.google/resolve?name=DOMAIN&type=A" — works from any shell, returns JSON.nslookup — works but some local resolvers may return "No response from server". Use only when 1 and 2 are unavailable.# A / NS / MX / CNAME / TXT via Google DNS-over-HTTPS
curl -s "https://dns.google/resolve?name=DOMAIN&type=A|NS|MX|CNAME|TXT"
# Indexed subdomains (HackerTarget)
curl -s "https://api.hackertarget.com/hostsearch/?q=DOMAIN"
Use these when "what nameservers did this domain use before migrating?" or "what DNS records existed historically?" matters. They reveal records that no longer resolve.
curl -s "https://crt.sh/?q=%.DOMAIN&output=json" — reveals subdomains that ever had SSL issued (indirect evidence they existed).https://securitytrails.com/domain/DOMAIN/dns (WebFetch; may require account).https://whoisfreaks.com/tools/dns/history/lookup/DOMAIN (WebFetch).https://dnshistory.org/dns-records/DOMAIN (WebFetch).https://viewdns.info/history/?domain=DOMAIN (WebFetch).Priority order for historical nameservers: SecurityTrails (preferred, comprehensive history) → WhoisFreaks → ViewDNS.info → DNS provider customer support.
https://who.is/whois/DOMAIN (WebFetch).https://lookup.icann.org/en/lookup?name=DOMAIN (WebFetch).wsl whois DOMAIN for shells with whois available.Note: some ccTLDs (.in, .de, .uk, etc.) do not expose public WHOIS for the registrant due to regional privacy regulations.
test cases passed, vs 15 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.