# Lookproof DNS TTL Lookup

> Lookproof DNS TTL Lookup is a paid API for AI agents from api.lookproof.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-31).

Returns the TTL of A, AAAA, MX, NS, TXT, CAA, and SOA records for a domain, sourced from DNSSEC-validated signatures or resolver cache, plus SOA negative caching TTL.

## Facts

- Endpoint: GET https://api.lookproof.dev/v1/dns/ttl?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lookproof-dns-ttl-lookup-1e4e1998
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KalrZKOmBTEMqcPufUAXg

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 lookproof-dns-ttl-lookup-1e4e1998
```

Example prompt: How long will the old A, MX, and NS records for stripe.com stay cached after I update them — can you check the current TTLs, including whether they come from a DNSSEC-validated signature or just the resolver's remaining cache time?

## When to prefer this

Choose this endpoint when you need to know how long existing DNS records will continue to be served from caches before a change propagates — especially when DNSSEC is in play and you need to distinguish between the authoritative RRSIG Original TTL and the resolver's remaining cache time. It is more informative than a plain DNS resolver for change-planning purposes, since it surfaces the TTL source. Prefer it over generic DNS resolution endpoints when planning DNS migrations, cutover timing, or auditing negative caching behavior.

## Known failure modes

- Domain does not exist — returns NXDOMAIN or empty result
- Domain has no records of a given type — that type omitted from response
- DNSSEC not enabled — TTL source will be resolver cache only, not RRSIG validated
- Invalid or malformed domain input — returns 400 validation error
- Resolver unreachable or timeout — returns 5xx error
- Domain string too long (over 1024 characters) — returns validation error

## How this service works

Check SPF, DMARC, DKIM, MTA-STS, DNSSEC and more, with results that explain what was found and why. Free browser checks and a pay-per-request API with x402.

## Output

A structured response listing each queried record type (A, AAAA, MX, NS, TXT, CAA, SOA) with its TTL value, the source of that TTL (either the DNSSEC RRSIG Original TTL from a validated signature, or the resolver's remaining cache time as a lower bound), and the SOA negative caching TTL for the domain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "title": "DomainInput",
     "required": [
      "domain"
     ],
     "properties": {
      "domain": {
       "type": "string",
       "title": "Domain",
       "examples": [
        "example.com"
       ],
       "maxLength": 1024,
       "minLength": 1
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lookproof-dns-ttl-lookup-1e4e1998/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.lookproof.dev](https://www.zero.xyz/host/api.lookproof.dev/llms.txt)