Fix Plan
pro/v1/reports/fix-planRuns the domain's email-security and DNS-security checks and emits a prioritized remediation action list. Each action carries priority (severity × impact), effort estimate, and dependency relationships — e.g., "fix DMARC" requires "fix SPF" first. Supports compact (top-5) and full (complete list) formats.
What It Does
Runs SPF, DMARC, DKIM, MTA-STS, and DNSSEC analysis in parallel. Filters out informational findings. Applies a category × severity weight matrix to compute per-finding priority. Maps each finding to an effort estimate (low/medium/high) and inter-category dependency graph. Sorts by priority descending. Returns the ordered action plan with remediation steps, effort, priority score, and predecessor actions that must be completed first.
Why It's Useful
Checker tools tell you what's wrong; fix plans tell you what to do next. Security teams running a scan get a laundry list of findings and no sequencing guidance — this endpoint turns raw findings into a sprint-ready backlog prioritized by impact and dependency order.
Use Cases
Hardening Sprint Planning
Quarterly hardening sprint: generate a fix plan per domain and use it as the sprint backlog.
Convert scan output to actionable, sequenced work items without manual triage.
Executive Remediation Reporting
Communicate the top 5 email-security actions per domain to leadership without surfacing protocol-level detail.
Compact plan format maps cleanly to executive summaries.
Consulting Deliverable
Deliver a prioritized fix plan per domain as a scan-report deliverable to clients.
Repeatable, structured plan output per engagement.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to generate a fix plan forExample: example.com |
detail | string | Optional | Output format: "compact" (top 5 actions) or "full" (complete list). Default: full.Example: fullOptions: compact, full |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The queried domain |
total_findings | number | Total non-informational findings across all categories |
action_count | number | Number of actions in the returned plan |
actions | array | Ordered action list: category, finding, severity, priority_score, effort, depends_on, remediation |
summary | object | Counts by severity and by category |
Code Examples
curl "https://api.edgedns.dev/v1/reports/fix-plan" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=example.com"const response = await fetch(
'https://api.edgedns.dev/v1/reports/fix-plan?domain=example.com',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/reports/fix-plan',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'example.com'
}
)
data = response.json()
print(data)Read the full Fix Plan guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.