Email authentication
GET
/api/v1/spf-checkerPacketFlo SPF Checker API
Cost: 1 credit per request
See which mail servers a domain authorizes to send for it.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain to check. |
Example request
curl "https://packetflo.io/api/v1/spf-checker?domain=example.com&api_key=YOUR_API_KEY"
Example response
{ "ok": true, "data": { "domain": "example.com", "found": true, "record": "v=spf1 ip4:192.0.2.0/24 include:_spf.google.com -all", "mechanisms": ["ip4:192.0.2.0/24", "include:_spf.google.com", "-all"], "multiple": false }, "meta": { "tool": "spf-checker", "version": "v1" } }
Reading the result
found indicates an SPF TXT record was found. multiple indicates more than one SPF record; record contains the first one.
Response fields
| Field | What it tells you |
|---|---|
record / found | The selected SPF record, or null when none was returned. |
mechanisms | Tokens after the SPF version, including mechanisms and modifiers. |
multiple | Whether the lookup returned multiple SPF records. |
Scope and limits
Reads DNS TXT records without recursively expanding includes, validating the lookup budget or testing a sender's authorization. DNS failures can appear as a missing record.
Authentication and errors
Send your key in the x-api-key header, or the supported api_key query parameter. Each request uses 1 credit from the key's shared 300-credit rolling 24-hour budget. Credits are charged before parameter validation. Successful responses and quota errors include usage headers; GET and OPTIONS support CORS.
| API status | Meaning |
|---|---|
200 | The diagnostic returned a result in data, with ok: true and version information in meta. Read the diagnostic fields to determine the target's condition. |
400 | Invalid or blocked input, or a lookup/check failure that could not be returned as a diagnostic result. Read error for details. |
401 | Missing, invalid or revoked API key. |
429 | The request would exceed the key's available credit budget. |