# Permissive SPF Policy Check for Vendor Screening

> Permissive SPF Policy Check for Vendor Screening is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Checks a domain's SPF DNS record for permissive policies ending in +all or ?all and lists the included mechanisms, flagging risky configurations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/demand-domain-spf-permissive-policy-vendor-screening?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/permissive-spf-policy-check-for-vendor-screening-b9f30cc5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9-PA_PBdH-XIY4XlVarjI

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 permissive-spf-policy-check-for-vendor-screening-b9f30cc5 -d '<json body>'
```

Example prompt: Can you check whether acme-supplier.com has a permissive SPF policy — specifically if it ends in +all or ?all — and list out all its SPF mechanisms?

## When to prefer this

Choose this endpoint when you need a fast, lightweight DNS-only check to screen vendor or partner domains for dangerous SPF permissiveness (+all or ?all) as part of a vendor risk or procurement workflow. It is ideal when you do not need full email deliverability testing or inbox verification — just a security flag on the SPF policy posture. Prefer this over a full email security audit tool when cost and speed matter and the question is specifically about SPF permissiveness.

## Known failure modes

- Domain has no SPF record — returns not found or no SPF record response
- Domain does not exist in DNS — returns DNS resolution failure
- Domain uses a valid but non-permissive SPF policy — returns not flagged with policy details
- Malformed SPF record — may return parse error or incomplete mechanism list
- Network or DNS timeout — returns service unavailable

## How this service works

Permissive SPF policy check for Vendor screening: Flag an SPF policy ending in +all or ?all and list its mechanisms. DNS data only; does not send email or verify that an inbox exists.

## Output

Returns whether the domain's SPF record uses a permissive qualifier (+all or ?all), along with a structured list of the SPF mechanisms found in the DNS TXT record. No email is sent and no inbox is verified — this is purely DNS-based lookup data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "default": "example.com",
   "description": "Public DNS domain, e.g. example.com."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/permissive-spf-policy-check-for-vendor-screening-b9f30cc5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)