Menu

Individual skill

dns-lookup

0upvotes

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.

plugins/pm-live/skills/dns-lookup/SKILL.md

Read pinned source

Source commit e0009a385c480fb0b5687e7412df67c7c64f7cee

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,542
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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:
Back to top