Verify DNS records

Check the health of your email DNS records for one or more domains.

This endpoint inspects the four essential email authentication records (MX, SPF, DKIM, and DMARC), compares them against the expected values for your email platform (Google Workspace or Microsoft 365), and cross-checks with Cloudflare to detect any inconsistencies.

You can verify a single domain by passing domain or uid, or verify up to 50 domains at once by passing domains or uids as an array. The response always returns a results array with per-domain verification details, along with an aggregated summary.

This is a read-only operation. No records are modified. To fix any issues found, use the Repair DNS Records endpoint.

What gets checked:

MX - Mail exchange record (controls where email is delivered)

SPF - Sender Policy Framework (controls who can send email on your behalf)

DKIM - DomainKeys Identified Mail (verifies email signatures)

DMARC - Domain-based Message Authentication (sets your email authentication policy)

Health statuses explained:

healthy - All four email records are correctly configured and in sync

critical - One or more records are missing or in an error state, which will likely cause email delivery failures

issues_found - Records exist but some have incorrect values, which may affect email authentication

unknown - No email platform could be detected for this domain

Per-record statuses:

ok - Record is present and has the correct value

missing - Record does not exist and needs to be created

misconfigured - Record exists but has an incorrect value

errored - Record failed to sync and needs to be re-synced

pending - Record was recently created or updated and is waiting to propagate

not_applicable - Record is not relevant for this domain (for example, DKIM before a mailbox has been set up)

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

application/json

DNS verification completed successfully. The response includes an aggregated summary and a results array with per-domain details.

Bodyapplication/json

curl --location 'https://api.inboxkit.com/v1/api/dns/verify' \ --header 'X-Workspace-Id;' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "domain": "example.com" }'

{ "error": false, "message": "Bulk DNS verification completed: 1 domain verified", "summary": { "total_requested": 1, "total_verified": 1, "total_failed": 0, "healthy": 1, "critical": 0, "issues_found": 0, "needs_repair": 0 }, "results": [ { "domain": "example.com", "domain_uid": "3340bae3-53c3-4ab8-9c61-1d8205b86c70", "status": "success", "platform": "GOOGLE", "cloudflare_checked": true, "overall_health": "healthy", "needs_repair": false, "records": [ { "label": "MX", "type": "MX", "host": "@", "status": "ok", "current_value": "smtp.google.com", "expected_value": "smtp.google.com", "issue": null, "fix_description": null }, { "label": "SPF", "type": "TXT", "host": "@", "status": "ok", "current_value": "v=spf1 include:_spf.google.com ~all", "expected_value": "v=spf1 include:_spf.google.com ~all", "issue": null, "fix_description": null }, { "label": "DMARC", "type": "TXT", "host": "_dmarc", "status": "ok", "current_value": "v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; ri=604800; aspf=s; adkim=s", "expected_value": "v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; ri=604800; aspf=s; adkim=s", "issue": null, "fix_description": null }, { "label": "DKIM", "type": "TXT", "host": "google._domainkey", "status": "ok", "current_value": "v=DKIM1; k=rsa; p=MIIBIjAN...", "expected_value": "v=DKIM1; k=rsa; p=MIIBIjAN...", "issue": null, "fix_description": null } ], "record_summary": { "total_checked": 4, "ok": 4, "missing": 0, "misconfigured": 0, "errored": 0, "pending": 0, "not_applicable": 0, "out_of_sync": 0 } } ] }

Verify DNS records

Request

Responses