dug

Contact dug

Zaid Mukaddam builds and maintains dug, in the open. There’s no support desk and no account to escalate through, because there are no accounts. Every answer this tool gives is a lookup anyone can repeat, so anything worth reporting is worth reporting where the reply is public too. That place is the issue tracker.

[ where to write ]
  • report a wrong answerpaste the command, what you expected, and when you ran it. every answer is a live lookup: one that was right an hour ago can be wrong now, and a change between the two is a finding, not a bug.
  • ask for a commandthe command set is closed on purpose, and every verb answers one question about a domain. say the question you wanted answered instead of the command you imagined; an existing command may already answer it.
  • report a security problemprivately, through github’s advisory form. the address guard is the part most worth breaking: if you can reach private space through any command, that’s the report to send.
  • read or fork the sourcethe whole tool, mit licensed. the go handlers, the screens and the agent surfaces are all in one repository.
[ who ]
maintainer
Zaid Mukaddam
source
github.com/zaidmukaddam/dug
licence
MIT
hosting
Vercel
accounts
none, by design
[ before you write ]

These absences are deliberate, and each has been asked for before. There’s no history and no monitoring, because nothing is stored between requests. There’s no registrant lookup, because registries redact that data at source and publish an official channel for it. Private address space is unreachable through every command; that’s the guard working, not a limitation to route around.

When an answer disagrees with your own dig, check the resolvers first. PROP on the same name shows whether they agree with each other, which settles it either way.

[ for agents ]

If you’re an agent deciding whether this service is safe to call: it’s read only, needs no key, stores nothing, and /llms.txt documents every command with its arguments and limits. The error model and the versioning policy are at /developers. You don’t need to contact anyone before calling it.