# BRAINIAC DNS Resolution Diagnosis

> BRAINIAC DNS Resolution Diagnosis is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.03/call, status unknown (last checked 2026-11-12).

Diagnoses DNS resolution issues by analyzing resolver logs, expected answers, and network data to identify mismatches, failures, and anomalies

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/network-intelligence/dns-resolution-diagnose?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-dns-resolution-diagnosis-8af8eeea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JwWIBHleO1OtfUPs9NYxm

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-dns-resolution-diagnosis-8af8eeea -d '<json body>'
```

Example prompt: Can you diagnose why api.example.com is resolving to 203.0.113.9 instead of the expected 198.51.100.9? Here are my resolver logs — check the A record and flag any mismatches or anomalies you find.

## When to prefer this

Use this endpoint when you need to diagnose DNS resolution correctness — especially when you have resolver logs, expected answers, and want to identify mismatches, failures, or anomalies across multiple hostnames. Prefer this over generic DNS lookup tools when you need structured health assessments, issue codes, and finding summaries rather than raw DNS query results. Ideal for post-deployment validation, incident triage, and security investigations into DNS hijacking or poisoning, paying only $0.03 USDC per call with no account required.

## Known failure modes

- Missing required hostname or DNS log data results in empty or incomplete diagnosis
- Unexpected record types not covered by schema may be ignored
- Truncated input (CSV/JSON over 200,000 chars) will be rejected
- If no resolver logs or expected answers are supplied, diagnosis has limited basis
- Public DNS lookup only performed if explicitly requested; otherwise analysis is limited to caller-supplied data
- Misformatted log entries may be skipped without error

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with per-hostname diagnosis items (health status, actual vs expected answer, record type, latency, issue codes like 'answer_mismatch'), aggregated findings with detail messages, counts of healthy and unhealthy records, timestamps, and flags indicating whether public DNS, TLS inspection, or paid reputation APIs were used. Each item includes whether the private network was scanned (never) and the data source.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "required": [
    "fileBase64"
   ],
   "properties": {
    "role": {
     "type": "string",
     "maxLength": 80
    },
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "text/plain",
      "text/csv",
      "application/json",
      "application/octet-stream"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "logs": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "at": {
      "type": "string",
      "maxLength": 40
     },
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "host": {
      "type": "string",
      "maxLength": 253
     },
     "source": {
      "type": "string",
      "maxLength": 200
     },
     "message": {
      "type": "string",
      "maxLength": 4000
     },
     "facility": {
      "type": "string",
      "maxLength": 80
     },
     "severity": {
      "type": "string",
      "maxLength": 40
     },
     "sourceIp": {
      "type": "string",
      "maxLength": 80
     },
     "destinationIp": {
      "type": "string",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "maxItems": 10000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "files": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "fileBase64"
    ],
    "properties": {
     "role": {
      "type": "string",
      "maxLength": 80
     },
     "filename": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
     },
     "mediaType": {
      "enum": [
       "text/plain",
       "text/csv",
       "application/json",
       "application/octet-stream"
      ],
      "type": "string"
     },
     "fileBase64": {
      "type": "string",
      "maxLength": 12000000,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 20
  },
  "configs": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "key": {
      "type": "string",
      "maxLength"
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "id": "D1",
    "rcode": "NOERROR",
    "answer": "93.184.216.34",
    "issues": [],
    "source": "Caller-supplied resolver log",
    "healthy": true,
    "hostname": "www.example.com",
    "resolver": "",
    "latencyMs": 12,
    "recordType": "A",
    "expectedAnswer": "93.184.216.34",
    "latencyMsSupplied": true,
    "privateNetworkScanned": false
   },
   {
    "id": "D2",
    "rcode": "NOERROR",
    "answer": "203.0.113.9",
    "issues": [
     "answer_mismatch"
    ],
    "source": "Caller-supplied resolver log",
    "healthy": false,
    "hostname": "api.example.com",
    "resolver": "",
    "latencyMs": 0,
    "recordType": "A",
    "expectedAnswer": "198.51.100.9",
    "latencyMsSupplied": false,
    "privateNetworkScanned": false
   }
  ],
  "status": "diagnosed",
  "findings": [
   {
    "code": "dns_mismatch",
    "kind": "conflict",
    "detail": "DNS answer \"203.0.113.9\" does not match expected \"198.51.100.9\".",
    "subject": "D2"
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "limitations": [
   "Network logs, latency/packet-loss samples, DNS answers, BGP routes, certificates, configs, reputation labels, and incidents are copied only from labeled fields supplied by the caller, or from optional key-free public DNS / public TLS port-443 inspection when explicitly requested.",
   "Private, loopback, link-local, and documentation addresses are never contacted. Private networks are not scanned.",
   "No intrusive security testing is performed and no paid reputation API is used.",
   "IP reputation uses only caller-supplied labels/observations. Missing reputation data is not invented.",
   "Infrastructure health reports aggregate only sections for which records were supplied or optionally fetched."
  ],
  "recordCount": 2,
  "apiKeyRequired": false,
  "unhealthyCount": 1,
  "paidProviderUsed": false,
  "publicDnsQueried": false,
  "publicTlsInspected": false,
  "paidReputationApiUsed": false,
  "privateNetworkScanned": false,
  "intrusiveScanPerformed": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-dns-resolution-diagnosis-8af8eeea/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
