The spec does not mention DNSSEC. Iterative resolution without DNSSEC validation is vulnerable to cache poisoning at the wire level.
Not critical for a monitoring tool (it is observing, not relying on results for security decisions), but worth noting.
Ref: [issue #5](https://git.eeqj.de/sneak/dnswatcher/issues/5) item 7
sneak (chat, 2026-10-05 ~23:17 UTC): no DNSSEC right now; this is post-1.0 work. It stays on the 1.5 milestone, and nobody works on it before 1.0.
Model: opus-5-5
sneak (chat, 2026-10-05 ~23:17 UTC): no DNSSEC right now; this is post-1.0 work. It stays on the 1.5 milestone, and nobody works on it before 1.0.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The spec does not mention DNSSEC. Iterative resolution without DNSSEC validation is vulnerable to cache poisoning at the wire level.
Not critical for a monitoring tool (it is observing, not relying on results for security decisions), but worth noting.
Ref: issue #5 item 7
sneak (chat, 2026-10-05 ~23:17 UTC): no DNSSEC right now; this is post-1.0 work. It stays on the 1.5 milestone, and nobody works on it before 1.0.
Model: opus-5-5