hunt-email-dns

Validates DNS records, email authentication, and reset callback bindings on owned domains.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-email-dns-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-email-dns
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-email-dns
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-email-dns-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers need a disciplined, evidence-gated way to verify whether their own domains' DNS configuration, email authentication (SPF, DKIM, DMARC), and password-reset or callback flows are correctly bound, without risking real mail delivery or spoofing. ## Core Features & Use Cases - DNS and Mail Authentication Review: Checks MX, SPF, DKIM, and DMARC records on owned domains with read-only DNS queries cross-validated against application logs. - Reset/Callback Binding Validation: Verifies sender, recipient, return-path alignment, token binding, and expiration in self-owned test mailboxes and no-op reset flows. - Evidence-Gated Oracles: Distinguishes real findings (reproducible misbinding between owned identities) from false positives like single DNS lint results or undelivered messages. - Use Case: During an authorized assessment of your own domain, use this Skill to confirm that a password-reset email cannot be misrouted to a different owned identity and that DMARC policy matches actual receiving behavior. ## Quick Start Use hunt-email-dns to plan an evidence-gated validation of my own domain's DNS records, email authentication, and password-reset binding.

Frequently Asked Questions about hunt-email-dns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate SPF, DKIM, and DMARC records for my domain?

Perform read-only DNS queries for the MX, SPF, DKIM, and DMARC records, then cross-validate the results against application and mail logs. A missing record alone is not exploitable; findings require reproducible evidence of policy mismatch.

How to test password reset email flows safely?

Use self-owned test mailboxes and no-op reset flows to check sender, recipient, and return-path alignment plus token binding and expiration. Never deliver to real recipients or third-party mailboxes during validation.

What counts as a real email security finding versus a false positive?

A valid finding reproducibly shows a reset or callback misbound to another owned identity, or a domain policy inconsistent with actual receiving behavior. Single DNS lint results, undelivered messages, and external domains do not qualify.

When should email DNS testing stop during an assessment?

Stop immediately upon real mail delivery, spoofing, third-party mailbox involvement, actual password-reset takeover, or any production side effect outside the written authorization window. Preserve DNS answers, audit logs, and timelines as evidence.

Can this approach test domains I do not own?

No. The workflow strictly requires owned accounts, domains, callbacks, and rollback-capable test data with documented authorization. Third-party assets and shared users are explicitly out of scope.