Validate Fix
developer/v1/reports/validate-fixGiven a domain and the check ID of a previously flagged finding (e.g., spf, dmarc, dkim, mta-sts, dnssec), re-runs that specific check and reports whether the fix appears to have applied. Useful as a post-remediation verification step.
What It Does
Accepts a domain plus check_id in the set {spf, dmarc, dkim, mta-sts, dnssec}. Runs that single check and returns fix_status: resolved (no findings of the same severity as before), partial (some findings remain), still_present (all findings remain), or worsened (new or elevated findings). Returns the current check result alongside so callers can see the full post-fix state.
Why It's Useful
Closes the remediation loop: run scan → generate fix plan → deploy records → validate fix. Teams need machine-readable evidence that a deployed change had the intended effect.
Use Cases
Post-Deploy Verification
After deploying an updated SPF record, confirm the fix applied before marking the ticket resolved.
Eliminate "looks fine" assumption-driven ticket closure.
Automated Remediation Pipelines
GitOps pipeline that publishes DNS changes can call validate-fix to gate the merge on a successful verification.
DNS changes that don't take effect fail the pipeline instead of silently merging.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to re-checkExample: example.com |
type | string | Required | The check to validate: spf, dmarc, dkim, mta-sts, or dnssecExample: spfOptions: spf, dmarc, dkim, mta-sts, dnssec |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The queried domain |
check_id | string | The check that was re-run |
fix_status | string | resolved | partial | still_present | worsened |
current_result | object | Current check output (score, grade, findings) |
summary | string | Human-readable one-line fix status |
Code Examples
curl "https://api.edgedns.dev/v1/reports/validate-fix" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=example.com" \
-d "type=spf"const response = await fetch(
'https://api.edgedns.dev/v1/reports/validate-fix?domain=example.com&type=spf',
{
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/validate-fix',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'example.com',
'type': 'spf'
}
)
data = response.json()
print(data)Read the full Validate Fix 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.
Try This Endpoint
Test the Validate Fix endpoint live in the playground.