# SPF Record Checker

> SPF Record Checker is a paid API for AI agents from agent402.tools, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-16).

Fetches and validates a domain's SPF record, parsing mechanisms and counting DNS lookups against the 10-lookup limit

## Facts

- Endpoint: POST https://agent402.tools/api/spf-check
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spf-record-checker-815a1488
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9B_s38BpOBqHm0nqnRQDl

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 spf-record-checker-815a1488 -d '<json body>'
```

Example prompt: Can you check the SPF record for example.com and tell me if it's valid, how many DNS lookups it uses, and whether the all mechanism is set to fail or softfail?

## When to prefer this

Use this endpoint when you need to validate or debug SPF configuration for a domain, especially when troubleshooting email deliverability, checking DNS lookup counts against the RFC 7208 10-lookup limit, or auditing the SPF policy qualifier on the 'all' mechanism. Prefer this over generic DNS tools when you specifically need structured SPF mechanism parsing and lookup counting.

## Known failure modes

- Domain has no SPF record — returns not-found or empty result
- Domain does not exist or is unreachable — DNS resolution failure
- SPF record exceeds 10 DNS lookup limit — flagged as invalid
- Malformed SPF record syntax — parse error returned
- Invalid input (non-domain string) — input validation error

## How this service works

Fetch and validate a domain's SPF record (RFC 7208). Parses mechanisms (ip4/ip6/include/a/mx/all), counts DNS lookups against the famous 10-lookup limit, and flags the qualifier on `all` (-/fail, ~/softfail, ?/neutral). The first stop when an email is hitting the spam folder.

## Output

Returns parsed SPF record data including all mechanisms (ip4, ip6, include, a, mx, all), the total DNS lookup count compared to the 10-lookup RFC limit, and the qualifier on the 'all' mechanism indicating the policy (-all for fail, ~all for softfail, ?all for neutral)

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "description": "Domain name (also accepts email/url/host)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "all": "softfail",
  "raw": "v=spf1 include:_spf.google.com ~all",
  "valid": true,
  "domain": "google.com",
  "warnings": [],
  "hasRecord": true,
  "mechanisms": [
   {
    "type": "include",
    "value": "_spf.google.com",
    "qualifier": "pass"
   },
   {
    "type": "all",
    "qualifier": "softfail"
   }
  ],
  "lookupCount": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/spf-record-checker-815a1488/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)