# ForgeMesh DNS Record Lookup

> ForgeMesh DNS Record Lookup is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Resolves any DNS record type (MX, A, AAAA, TXT, etc.) for a hostname and returns full record details with DNSSEC validation status as JSON.

## Facts

- Endpoint: POST https://x402.forgemesh.io/mx-record-lookup
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-dns-record-lookup-090ae09d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u_uawPf0d3BelhEk7lMxV

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 forgemesh-dns-record-lookup-090ae09d -d '<json body>'
```

Example prompt: Can you look up the MX records for sendgrid.com and tell me if DNSSEC is valid?

## When to prefer this

Use this endpoint when you need structured DNS record data with DNSSEC validation status for any record type, especially for checking email deliverability setup (MX, SPF, DKIM TXT records), verifying domain ownership, or infrastructure monitoring — particularly when you need cached, JSON-formatted results without running your own DNS resolver.

## Known failure modes

- Invalid hostname format returns error
- Unknown or unsupported record type may return empty records array
- Non-existent domain returns NXDOMAIN or empty result
- DNSSEC validation failure indicated in status field
- Network or upstream resolver timeout

## How this service works

Query mail server (MX), address (A/AAAA), text (TXT), or any other DNS record type for a hostname, with DNSSEC validation status and the full set of returned records — name, type, TTL, and data — as JSON. Useful for checking email deliverability setup, verifying domain ownership, and infrastructure monitoring. Results cached 5 minutes.

## Output

A JSON object containing the DNSSEC validation status and an array of DNS records each with name, type, TTL, and data fields, cached for up to 5 minutes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "Hostname to resolve, e.g. example.com"
  },
  "type": {
   "type": "string",
   "description": "Record type, default A"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "Answer": [
    {
     "TTL": 3600,
     "data": "0 .",
     "name": "example.com",
     "type": 15
    }
   ],
   "Status": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-dns-record-lookup-090ae09d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)
