DNS Doctor - Email & DMARC
dev.dnsdoctor/dns-doctor
Tools
Exactly what the server advertised in the scan completed . Effects and capabilities are classified by Squatch from each tool's metadata. Squatch never runs tools. Compared with the previous scan: 0 new, 5 changed.
- Effect: Read 24
- Effect: Write 4
- Effect: Execute 1
Showing 29 of 29 tools
| Details | ||
|---|---|---|
| build_parked_domain_records Use this when the user asks how to protect a domain that sends no email from being spoofed. Build the three-record hardening pack that make… | Effect: Execute | |
| add_monitored_domain Add a domain to the signed-in user's DNS Doctor monitoring and return the ownership-check TXT record they must publish, plus where their DN… | Effect: Write | |
| build_dmarc_upgrade Use this when the user asks how to move DMARC on from p=none, whether it is safe to tighten DMARC, or what the next DMARC policy step is fo… | Effect: Write | |
| start_email_test Use this when the user wants to know how a real email from them actually authenticates — whether a message from Google Workspace, Microsoft… | Effect: Write | |
| start_monitoring_signup Use this when the user asks for ongoing DMARC monitoring, RUA report monitoring, new-sender monitoring, email-authentication alerts, ongoin… | Effect: Write | |
| audit_spf_includes Use this when the user asks who can send email as their domain through SPF includes, or wants an SPF supply-chain or third-party sender aud… | Effect: Read | |
| check_bimi Use this when the user asks how to get their logo shown in Gmail, Yahoo, Apple Mail or other inboxes (BIMI), whether their BIMI setup works… | Effect: Read | |
| check_dkim_selector Use this when the user asks whether DKIM is set up for a sending platform, whether a specific selector exists, or why DKIM fails. Check ONE… | Effect: Read | |
| check_domain_names Use this when the user is choosing a domain name and wants to know which candidates are already registered. Pass up to 20 candidate names i… | Effect: Read | |
| check_domain_verification Use this only for DNS Doctor's own ownership TXT challenge on a domain the user already added to their DNS Doctor account (add_monitored_do… | Effect: Read | |
| check_lookalikes Use this when the user asks about lookalike, look-alike, typosquat or impersonation domains of their domain, or whether someone has registe… | Effect: Read | |
| check_propagation Use this when the user asks whether a DNS change has propagated globally, or why a record shows in one place and not another. Check whether… | Effect: Read | |
| check_record Use this when the user asks whether a DNS change has landed, wants a DNS record looked up, or wants to verify a record they just published … | Effect: Read | |
| check_reverse_dns Use this when the user asks about reverse DNS, PTR records, or FCrDNS for a mail server IP. Check one sending IP's forward-confirmed revers… | Effect: Read | |
| count_spf_lookups Use this when the user asks about SPF 'too many lookups', the 10-lookup limit, an SPF PermError, or whether an SPF record is valid. Validat… | Effect: Read | |
| generate_dmarc_record Use this when the user asks to create, generate or write a DMARC record for a domain that has none. Build a DMARC record from scratch for a… | Effect: Read | |
| get_alertsChanged Use this when a signed-in operator asks what changed on a monitored domain, whether its website went down, or what the monitoring has flagg… | Effect: Read | |
| get_domain_records Read the records a domain the user monitors still needs: the ownership check while it is unverified, and once verified the DMARC reporting … | Effect: Read | |
| get_email_test Use this after start_email_test, once the user says they sent the email. Returns status pending | received | expired | error. pending means… | Effect: Read | |
| get_lookalikesChanged Use this when a signed-in operator asks which lookalike domains of a monitored domain the watch has found, how risky they are, or for one's… | Effect: Read | |
| get_readinessChanged Use this when a signed-in operator asks whether a monitored domain is ready for the next DMARC step. Read the DMARC enforcement-readiness v… | Effect: Read | |
| get_report Use this for the same questions as scan_domain when a recent report is enough (the cheap first look); use scan_domain when the state must b… | Effect: Read | |
| list_email_testsChanged Use this when a signed-in user asks about email tests they ran before, or how a sender's earlier tests scored. Needs a connected DNS Doctor… | Effect: Read | |
| list_my_domainsChanged Use this when a signed-in operator asks which domains their DNS Doctor account monitors, or what to do next on them. Lists every domain on … | Effect: Read | |
| lookup_registration Use this when the user asks who owns a domain, when it expires, which registrar or nameservers it has, whether it is registered, or whether… | Effect: Read | |
| parse_dmarc_report Use this when the user uploads or pastes a DMARC aggregate (RUA) XML report and asks what it says. Parse ONE DMARC aggregate (RUA) report i… | Effect: Read | |
| scan_domain Use this when the user asks to check, audit, diagnose or troubleshoot SPF, DKIM, DMARC, email authentication, email deliverability DNS, why… | Effect: Read | |
| validate_dmarc_record Use this when the user pastes a DMARC record and asks whether it is valid, correct or safe. Validate a pasted DMARC record: parsed tags, le… | Effect: Read | |
| watch_record_change Use this when the user asks to be told when a DNS change they are making has finished ("let me know when it's live"). Starts a free watch o… | Effect: Read |