DNS Doctor integration researchA little less busywork with DNS Doctor.
Research only. Grunt is prelaunch, live service is paused, and live provider connections and outcomes remain unverified. The operations and examples below are not confirmed live Grunt features or approved supplier commitments.
Explore possible DNS Doctor workflows with Grunt. Documented operations include Domain: Add a domain to monitoring; Domain: Build the next safe DMARC record for a domain; Domain: Check whether a domain ownership record is visible. Actions on this page are research candidates from public integration definitions, not confirmation that Grunt support is live.
Exploratory scope only: these candidates come from public integration definitions and are not confirmed as live Grunt features.
DNS Doctor
“Explore whether a Grunt integration could add a domain to monitoring, then build the next safe dmarc record for a domain in DNS Doctor. Show me the result and wait for my approval before changing anything.”
Illustrative steps and outcome; no real work is performed here.
- 01Domain: Add a domain to monitoring
- 02Domain: Build the next safe DMARC record for a domain
- 03Review the result before anything changes
A clearer next step, with the final say still yours.
Explore possibilities with DNS Doctor.
Researched operations, not a list of enabled Grunt actions. Actual support, account permissions, supplier terms, and live acceptance require separate verification.
17 researched capabilities across 3 groups
- Add a domain to monitoring
Adds a domain to the token account's monitoring and returns the ownership TXT record to publish. Requires a credential with the domains:manage scope.
- Build the next safe DMARC record for a domain
The next safe DMARC record (alignment-gated) with the rationale. The record can be null; then the rationale is the answer.
- Check whether a domain ownership record is visible
Re-checks the ownership TXT record and marks the domain verified on a match. A transient outcome is our lookup, never a verdict about the DNS.
- Get the records a monitored domain still needs
The ownership record while unverified, and the DMARC reporting record once verified. Read-only.
- Get a monitoring signup link for a domain
A link that carries the domain into paid monitoring, for a human to open. Nothing is created and no email is sent.
- Get the persisted report for a domain
The last persisted report, or a fresh scan when none exists
- Scan a domain
SPF, DKIM, DMARC, MX, DNS health, blacklists and expiry with deterministic per-check verdicts and copy-paste fix records
Proposed setup considerations
The research notes below describe a possible setup. They are not instructions for an available Grunt connection; actual steps depend on supported operations and provider approval.
- 01
Start with a small, useful task.
Describe a routine step involving DNS Doctor. Keep a first version easy to review and change.
- 02
Plan the account access.
Check which DNS Doctor account, data, and permissions a safe connection would need. Start with the least access that can do the job.
- 03
Test the details together.
Validate a sample against a disposable account. Confirm which records are read, what could change, and how errors or duplicates are handled.
- 04
Keep the say-so.
Decide which steps could run on their own and which would need your review. Expand access only when the workflow needs it.
RESEARCH NOTES
Questions about the concept.
These notes describe possible uses. Customer availability remains unverified.
What could a Grunt integration do with DNS Doctor?
The documented operations include Domain: Add a domain to monitoring; Domain: Build the next safe DMARC record for a domain; Domain: Check whether a domain ownership record is visible; Domain: Get the records a monitored domain still needs. These are research candidates from public integration definitions and need validation and Grunt implementation before they can be treated as supported capabilities.
Could I keep a workflow read-only?
The research candidates do not confirm an implemented DNS Doctor connection or a read-only access mode. If built, verify least-privilege scopes and reject writes at the app API boundary.
Will every action run automatically?
If a connection is built, choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in DNS Doctor?
A future integration should let you decide which work could run on its own and which steps need your review.
A little less busywork.
A little more you.
Read the current prelaunch status and confirmed prices.
View pricing status Explore the simulation