dns-lookup
Query DNS records and domain registration data with zero API keys — DNS-over-HTTPS via dns.google and domain registration via RDAP, through plain curl. Use when asked what does this domain resolve to, check the MX or TXT records, who registered this domain, when does it expire, or has DNS propagated. Produces the records decoded (SPF/DKIM/DMARC read, not just dumped), the registration facts from RDAP, and the rerunnable commands.
npx skills add mohitagw15856/pm-claude-skills --skill dns-lookup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# DNS Lookup Skill DNS questions ("did the record propagate," "where's mail for this domain going," "who owns this") come with two keyless answers: Google's DNS-over-HTTPS for records, and RDAP — WHOIS's structured successor — for registration. This skill queries both, and does the part `dig` doesn't: decoding what the records *mean* — an SPF string into its policy, MX priorities into the actual mail provider, an expiry date into "renews in 6 weeks." ## What This Skill Produces - **The records** — A/AAAA/MX/TXT/CNAME/NS/whatever was asked, with TTLs - **The decode** — mail provider identified from MX, SPF/DMARC policies read out, CNAME chains followed - **Registration facts** — registrar, creation/expiry dates, status codes (from RDAP; contact data is mostly redacted now, and the answer says so) - **The commands** — exact curls, rerunnable ## Required Inputs Ask for these if not provided: - **The domain** — and the record type if the question implies one ("where's mail going" → MX; "is the site moved" → A/CNAME; "verify ownership token" → TXT) - **The scenario** — propagation check, email debugging, domain due-diligence, expiry watch — the decode leads with it ## Framework: The Two
- What This Skill Produces
- Required Inputs
- Framework: The Two Protocols
- Output Format
- Quality Checks
- Anti-Patterns
What does the dns-lookup skill do?
Query DNS records and domain registration data with zero API keys — DNS-over-HTTPS via dns.google and domain registration via RDAP, through plain curl. Use when asked what does this domain resolve to, check the MX or TXT records, who registered this domain, when does it expire, or has DNS propagated. Produces the records decoded (SPF/DKIM/DMARC read, not just dumped), the registration facts from RDAP, and the rerunnable commands.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill dns-lookup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.