Domain Health
by Domain Health Check API in Developer tools
Domain Health Check API. Check domain DNS, MX, SPF, DMARC, and email configuration health and receive a structured JSON score with issues and recommendations. Useful for agents, developers, email deliverability checks, domain diagnostics, infrastructure investigation, and security workflows. Paid per call via x402.
https://tools.ipintel.ai/domain-health- Price
- $0.001
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 675 ms
- 1.1 s slowest 5%
- Last check
- Passed
- 35 min ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://tools.ipintel.ai/domain-health
Each call costs $0.001 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://tools.ipintel.ai/domain-health
content-type: application/json
{
"domain": "ipintel.ai"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain name to analyze |
Example response
The provider's example. We can't check it without paying.
Example response, 29 lines
{
"dns": {
"a": [
"104.21.0.211"
],
"aaaa": [
"2606:4700:3033::6815:d3"
],
"dmarc": "v=DMARC1; p=none",
"mx": [
{
"host": "mx1.hostinger.com",
"priority": 5
}
],
"ns": [
"frank.ns.cloudflare.com",
"journey.ns.cloudflare.com"
],
"spf": "v=spf1 include:_spf.mail.hostinger.com ~all"
},
"domain": "ipintel.ai",
"issues": [],
"ok": true,
"score": 100,
"service": "domain_health",
"status": "good",
"timestamp": "2026-06-22T18:15:01+00:00"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.001.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://tools.ipintel.ai/domain-health' \
-H 'content-type: application/json' \
--data-raw '{"domain":"ipintel.ai"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://tools.ipintel.ai/domain-health' \
-H 'content-type: application/json' \
--data-raw '{"domain":"ipintel.ai"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ftools.ipintel.ai%2Fdomain-health&method=POST
const res = await pay("https://tools.ipintel.ai/domain-health", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"domain": "ipintel.ai"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://tools.ipintel.ai/domain-health",
json={
"domain": "ipintel.ai",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 35 min ago | Passed | 402 | 909 ms | $0.001 |
| 4 h ago | Passed | 402 | 603 ms | $0.001 |
| 7 h ago | Passed | 402 | 644 ms | $0.001 |
| 10 h ago | Passed | 402 | 806 ms | $0.001 |
| 13 h ago | Passed | 402 | 493 ms | $0.001 |
Show 10 older checks
| 16 h ago | Passed | 402 | 446 ms | $0.001 |
| 19 h ago | Passed | 402 | 848 ms | $0.001 |
| 23 h ago | Passed | 402 | 573 ms | $0.001 |
| 28 h ago | Passed | 402 | 623 ms | $0.001 |
| 33 h ago | Passed | 402 | 576 ms | $0.001 |
| 38 h ago | Passed | 402 | 646 ms | $0.001 |
| 44 h ago | Passed | 402 | 486 ms | $0.001 |
| 2 days ago | Passed | 402 | 1.1 s | $0.001 |
| 2 days ago | Passed | 402 | 546 ms | $0.001 |
| 2 days ago | Passed | 402 | 713 ms | $0.001 |