Documentation
Agent ToolsPOST

Agent Dns Checker

Check DNS records for a domain (A, AAAA, MX, NS, TXT, SPF, DMARC). Each record type is returned as `{type, values, found}`. `found: false` means no records of that type exist — treat this as a signal of misconfiguration when validating sender domains. SPF is extracted from TXT records automatically. DMARC is queried from the `_dmarc.<domain>` subdomain. Results are cached for 5 minutes. The `cached` field is `true` when the response was served from cache. Example request: {"domain": "gmail.com"} Signals agents should act on: - mx.found == false → domain cannot receive email - spf.found == false → no SPF record, higher spam risk - dmarc.found == false → no DMARC policy, spoofing risk Use POST /v1/agent/tools/dns-checker when you need this capability from your application or backend. It accepts a JSON request body. There are no query parameters for this operation.

Endpoint

Use this full URL directly in server-side integrations, scripts, or internal tooling.

POST request
https://api.dropfakes.com/api/v1/agent/tools/dns-checker
Full endpoint URL
POST https://api.dropfakes.com/api/v1/agent/tools/dns-checker

Authorization

This section explains how this endpoint should be called in the current API version.

No authorization required
This endpoint is documented as public in this version of the API reference. No bearer token is required.
Authorization
Authorization: dk_live_*****

Code examples

Start with curl, then use the language sample that matches your backend.

curl
curl -X POST "https://api.dropfakes.com/api/v1/agent/tools/dns-checker" \
  -H "Content-Type: application/json" \
  -d '{
  "domain": "example.com"
}'

Parameters

Query string parameters and request body fields are listed together for faster scanning.

NameLocationTypeRequiredDescriptionDefault
domainbodystringYesBody field for `domain`.-

Success response

The primary success status for this operation is 200.

Status 200
Successful Response
200 application/json
{
  "domain": "example.com",
  "a": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "aaaa": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "mx": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "ns": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "txt": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "spf": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "dmarc": {
    "type": "string",
    "values": [
      "string"
    ],
    "found": false
  },
  "cached": false
}

Error response

Use this example to handle validation and request errors safely on the client or backend.

Status 422
Validation Error
422 application/json
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}