# DKIM Public Key Lookup

> DKIM Public Key Lookup is a paid API for AI agents from agent402.tools, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Fetches and parses the DKIM TXT record at <selector>._domainkey.<domain>, returning key algorithm, length, and flags for rotation/strength verification.

## Facts

- Endpoint: POST https://agent402.tools/api/dkim-lookup
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dkim-public-key-lookup-19297331
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m-uv-MjXMNZYvRqANf94q

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 dkim-public-key-lookup-19297331 -d '<json body>'
```

Example prompt: Can you look up the DKIM public key for example.com using the selector 'google' and tell me the algorithm, key length, and any flags set?

## When to prefer this

Use this endpoint when you need to programmatically inspect a DKIM public key record for a known selector — for example, auditing key strength, confirming rotation after a key change, or verifying a domain's email authentication setup. Prefer this over manual DNS tools when you need structured parsed output (algorithm, key length, flags) rather than a raw TXT string.

## Known failure modes

- DKIM record not found — selector or domain does not exist in DNS
- Invalid domain format — domain cannot be resolved
- Selector not specified or incorrect — wrong selector name returns no record
- DNS lookup timeout — transient network error
- Malformed DKIM TXT record — cannot be parsed

## How this service works

Fetch and parse a DKIM public-key record at <selector>._domainkey.<domain> (RFC 6376). Returns the parsed key params (algorithm, length, flags) so you can verify rotation status or key strength. Caller must know the selector - use email-deliverability if you don't.

## Output

Returns parsed DKIM record parameters including the public key algorithm (e.g. RSA), key bit length (e.g. 2048), flags, and other key metadata from the DNS TXT record at <selector>._domainkey.<domain>.

## Example request

```json
{
 "domain": "example.com",
 "selector": "google"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Domain name (also accepts email/url/host)"
  },
  "selector": {
   "type": "string",
   "description": "DKIM selector, e.g. \"default\", \"google\", \"selector1\""
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "raw": "v=DKIM1; k=rsa; p=MIIBIj...",
  "flags": [],
  "domain": "google.com",
  "keyType": "rsa",
  "version": "DKIM1",
  "fullName": "20221208._domainkey.google.com",
  "selector": "20221208",
  "warnings": [],
  "hasRecord": true,
  "publicKey": {
   "bits": 2048,
   "base64": "MIIBIj...",
   "revoked": false
  },
  "serviceType": "*",
  "hashAlgorithms": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dkim-public-key-lookup-19297331/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)