DNS and email configuration signals
Domain health signals for production workflows.
Check public DNS, MX, SPF, DMARC and TLS certificate signals through one structured API response.
POST /v1/domain/check
curl -X POST https://api.antops.dev/v1/domain/check \
-H "X-API-Key: YOUR_RAPIDAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"domain": "example.com"
}'200 OK
{
"domain": "example.com",
"score": 82,
"status": "good",
"issues": [],
"recommendations": []
}Capabilities
One input. Useful signals.
Use cases
Designed for engineering workflows.
- Validate customer domains during onboarding
- Flag missing email authentication before a campaign launch
- Add a DNS and TLS signal to a SaaS account health workflow
Integrate
Keep the workflow yours.
- Call from a signup webhook after domain verification
- Run a scheduled review for managed domains
- Store the score and recommendations alongside account metadata
Scope and limitations
Signals, not unsupported promises.
- The result is a technical signal, not an inbox-placement guarantee.
- Only publicly routable domains are accepted.
- DNS and certificate state can change after a check completes.
FAQ
Before you call the API.
What does the Domain Health API check?
It checks public DNS, nameservers, MX, SPF, DMARC and TLS certificate signals for a single domain.
Can it check multiple domains?
Yes. The bulk endpoint accepts up to ten public domains; each checked domain consumes one monthly request.
Does a high score guarantee deliverability?
No. It reports technical configuration signals and does not guarantee delivery or inbox placement.
Ready to integrate