CaptainDNS

- Before a launch (new domain, new sending platform).
- After an SPF/DKIM/DMARC change.
- As soon as you see rejects like "SPF fail/DKIM fail/DMARC fail".

- Run an email audit on captaindns.com and explain what blocks delivery.
- Analyze captaindns.com: which SPF/DKIM/DMARC records should I fix first?

- Ascore(and a grade) to estimate "send readiness".
- Checksfor SPF/DKIM/DMARC (and BIMI if available), with an operational summary.
- A more detailed mode to understandwhyit passes / doesn't pass.

- If the widget flags an SPF/DKIM/DMARC issue: fix the DNS record, then re-run the audit.
- If you just changed a DNS record: follow withdns_propagationto verify visibility across resolvers.

- Right after a DNS change (SPF, DKIM, DMARC, MX, CNAME).
- When a test "works for me" but not for a recipient / third-party tool.
- To quantify consistency (score) instead of relying on a single resolver.

- Test DNS propagation of the SPF TXT for captaindns.com.
- Check propagation of TXT _dmarc.captaindns.com.
- Run dns_propagation for captaindns.com in TXT and summarize response groups.

- Aconsistency score(0-100) and astatus(OK / in progress / inconsistent / error).
- Response groups(observed values) and aTTL/estimateview.
- Anexpertview: resolver matrix, TTL per resolver, errors (SERVFAIL, etc.) and reproduction help (thedigcommand).

- Low score / multiple groups: wait for TTL to expire, or fix a divergence (secondary zone, DNS provider, split-horizon).
- Errors: make sure the record exists, NS delegation is healthy, and the queried resolver is not filtering.

- InSettings → Connectors, open the connector and clickRefresh, then test again in a new conversation.

No, ChatGPT can discover tools via the connector. In practice, for a quick diagnosis (or if in doubt), name the tool explicitly:email_auth_audit,dns_propagation,email_header_audit.