SPF Validator checks the Sender Policy Framework (SPF) DNS record for a domain to verify if it’s valid and optionally whether a given IP address is authorized to send emails for that domain.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// SPF Validator response payload
}
}
About the SPF Validator API
This tool performs a DNS lookup to retrieve the SPF record for the domain and validates its syntax, structure, and IP ranges. When an IP address is provided, the API tests whether it is permitted under the domain’s SPF rules for sending mail.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use SPF Validator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the SPF Validator API do?
How do I authenticate SPF Validator API requests?
How much does the SPF Validator API cost?
How fast is the SPF Validator API?
What response formats does the SPF Validator API support?
What HTTP method does the SPF Validator API use?
Request parameters — GET /v1/spfvalidator
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
domainRequired | string | myspace.com | The domain to validate the SPF record for domain |
curl "https://api.apiverve.com/v1/spfvalidator?domain=myspace.com" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/spfvalidator
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"host": "myspace.com",
"has_spf_record": true,
"dns_lookups_num": 9,
"spf_record": "v=spf1 mx ip4:63.208.226.34 ip4:204.16.32.0/22 ip4:67.134.143.0/24 ip4:216.205.243.0/24 ip4:34.85.156.5/32 ip4:35.245.108.108/32 ip4:34.86.129.193/32 ip4:34.86.134.94/32 ip4:34.85.222.234/32 ip4:34.86.176.234/32 ip4:34.86.125.212/32 ip4:34.85.224.60/32 ip4:34.86.160.49/32 ip4:35.245.64.166/32 ip4:35.188.226.11/32 ip4:34.86.208.228/32 ip4:34.85.216.144/32 ip4:35.221.22.153/32 ip4:34.86.137.108/32 ip4:34.86.51.35/32 ip4:34.150.221.40/32 ip4:34.85.216.70/32 ip4:34.86.37.191/32 ip4:34.85.214.215/32 ip4:35.236.234.82/32 ip4:34.86.161.241/32 ip4:216.32.181.16 ip4:216.178.32.0/20 ip4:168.235.224.0/24 include:_netblocks.mimecast.com -all",
"spf_records_list": [
{
"origin": "myspace.com",
"record": "v=spf1 mx ip4:63.208.226.34 ip4:204.16.32.0/22 ip4:67.134.143.0/24 ip4:216.205.243.0/24 ip4:34.85.156.5/32 ip4:35.245.108.108/32 ip4:34.86.129.193/32 ip4:34.86.134.94/32 ip4:34.85.222.234/32 ip4:34.86.176.234/32 ip4:34.86.125.212/32 ip4:34.85.224.60/32 ip4:34.86.160.49/32 ip4:35.245.64.166/32 ip4:35.188.226.11/32 ip4:34.86.208.228/32 ip4:34.85.216.144/32 ip4:35.221.22.153/32 ip4:34.86.137.108/32 ip4:34.86.51.35/32 ip4:34.150.221.40/32 ip4:34.85.216.70/32 ip4:34.86.37.191/32 ip4:34.85.214.215/32 ip4:35.236.234.82/32 ip4:34.86.161.241/32 ip4:216.32.181.16 ip4:216.178.32.0/20 ip4:168.235.224.0/24 include:_netblocks.mimecast.com -all",
"chars_num": 637,
"use_macro": false,
"domains": [
"_netblocks.mimecast.com"
],
"authorized_ips": {
"ipv4": [
"63.208.226.34",
"204.16.32.0/22",
"67.134.143.0/24",
"216.205.243.0/24",
"34.85.156.5/32",
"35.245.108.108/32",
"34.86.129.193/32",
"34.86.134.94/32",
"34.85.222.234/32",
"34.86.176.234/32",
"34.86.125.212/32",
"34.85.224.60/32",
"34.86.160.49/32",
"35.245.64.166/32",
"35.188.226.11/32",
"34.86.208.228/32",
"34.85.216.144/32",
"35.221.22.153/32",
"34.86.137.108/32",
"34.86.51.35/32",
"34.150.221.40/32",
"34.85.216.70/32",
"34.86.37.191/32",
"34.85.214.215/32",
"35.236.234.82/32",
"34.86.161.241/32",
"216.32.181.16",
"216.178.32.0/20",
"168.235.224.0/24"
]
}
},
{
"origin": "_netblocks.mimecast.com",
"record": "v=spf1 include:eu._netblocks.mimecast.com include:us._netblocks.mimecast.com include:za._netblocks.mimecast.com include:de._netblocks.mimecast.com include:au._netblocks.mimecast.com include:ca._netblocks.mimecast.com include:usb._netblocks.mimecast.com ~all",
"chars_num": 257,
"use_macro": false,
"domains": [
"eu._netblocks.mimecast.com",
"us._netblocks.mimecast.com",
"za._netblocks.mimecast.com",
"de._netblocks.mimecast.com",
"au._netblocks.mimecast.com",
"ca._netblocks.mimecast.com",
"usb._netblocks.mimecast.com"
]
},
{
"origin": "eu._netblocks.mimecast.com",
"record": "v=spf1 ip4:195.130.217.0/24 ip4:91.220.42.0/24 ip4:146.101.78.0/24 ip4:207.82.80.0/24 ip4:213.167.81.0/25 ip4:193.7.207.0/25 ip4:213.167.75.0/25 ip4:185.58.85.0/24 ip4:185.58.86.0/24 ip4:193.7.206.0/25 ip4:147.28.36.0/24 ~all",
"chars_num": 225,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"195.130.217.0/24",
"91.220.42.0/24",
"146.101.78.0/24",
"207.82.80.0/24",
"213.167.81.0/25",
"193.7.207.0/25",
"213.167.75.0/25",
"185.58.85.0/24",
"185.58.86.0/24",
"193.7.206.0/25",
"147.28.36.0/24"
]
}
},
{
"origin": "us._netblocks.mimecast.com",
"record": "v=spf1 ip4:207.211.31.0/25 ip4:205.139.110.0/24 ip4:216.205.24.0/24 ip4:170.10.129.0/24 ip4:63.128.21.0/24 ip4:170.10.133.0/24 ip4:185.58.84.93/32 ip4:207.211.41.113/32 ip4:207.211.30.64/26 ip4:207.211.30.128/25 ip4:216.145.221.0/24 ip4:170.10.128.0/24 ip4:170.10.132.56/29 ip4:170.10.132.64/29 ~all",
"chars_num": 299,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"207.211.31.0/25",
"205.139.110.0/24",
"216.205.24.0/24",
"170.10.129.0/24",
"63.128.21.0/24",
"170.10.133.0/24",
"185.58.84.93/32",
"207.211.41.113/32",
"207.211.30.64/26",
"207.211.30.128/25",
"216.145.221.0/24",
"170.10.128.0/24",
"170.10.132.56/29",
"170.10.132.64/29"
]
}
},
{
"origin": "za._netblocks.mimecast.com",
"record": "v=spf1 ip4:41.74.192.0/22 ip4:41.74.200.0/23 ip4:41.74.196.0/22 ip4:41.74.204.0/23 ip4:41.74.206.0/24 ~all",
"chars_num": 106,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"41.74.192.0/22",
"41.74.200.0/23",
"41.74.196.0/22",
"41.74.204.0/23",
"41.74.206.0/24"
]
}
},
{
"origin": "de._netblocks.mimecast.com",
"record": "v=spf1 ip4:51.163.158.0/24 ip4:194.104.109.0/24 ip4:194.104.111.0/24 ip4:194.104.110.21/32 ip4:194.104.110.240/28 ip4:62.140.10.21/32 ip4:62.140.7.0/24 ip4:194.104.108.240/29 ip4:194.104.108.21/32 ip4:51.163.159.0/24 ~all",
"chars_num": 221,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"51.163.158.0/24",
"194.104.109.0/24",
"194.104.111.0/24",
"194.104.110.21/32",
"194.104.110.240/28",
"62.140.10.21/32",
"62.140.7.0/24",
"194.104.108.240/29",
"194.104.108.21/32",
"51.163.159.0/24"
]
}
},
{
"origin": "au._netblocks.mimecast.com",
"record": "v=spf1 ip4:103.13.69.0/24 ip4:124.47.150.0/24 ip4:124.47.189.0/24 ip4:103.96.23.0/24 ip4:103.96.21.0/24 ip4:180.189.28.0/24 ip4:216.145.217.0/24 ip4:103.96.22.96/28 ip4:103.96.22.22/32 ip4:103.96.20.22/32 ip4:103.96.20.96/28 ~all",
"chars_num": 229,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"103.13.69.0/24",
"124.47.150.0/24",
"124.47.189.0/24",
"103.96.23.0/24",
"103.96.21.0/24",
"180.189.28.0/24",
"216.145.217.0/24",
"103.96.22.96/28",
"103.96.22.22/32",
"103.96.20.22/32",
"103.96.20.96/28"
]
}
},
{
"origin": "ca._netblocks.mimecast.com",
"record": "v=spf1 ip4:170.10.145.0/24 ip4:170.10.147.0/24 ip4:170.10.144.126/32 ip4:170.10.146.126/32 ip4:170.10.144.240/29 ip4:170.10.146.240/29 ip4:216.145.216.0/24 ~all",
"chars_num": 160,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"170.10.145.0/24",
"170.10.147.0/24",
"170.10.144.126/32",
"170.10.146.126/32",
"170.10.144.240/29",
"170.10.146.240/29",
"216.145.216.0/24"
]
}
},
{
"origin": "usb._netblocks.mimecast.com",
"record": "v=spf1 ip4:170.10.151.0/24 ip4:170.10.153.0/24 ip4:170.10.150.240/29 ip4:170.10.152.240/29 ip4:170.10.156.0/24 ip4:170.10.157.0/24 ~all",
"chars_num": 135,
"use_macro": false,
"authorized_ips": {
"ipv4": [
"170.10.151.0/24",
"170.10.153.0/24",
"170.10.150.240/29",
"170.10.152.240/29",
"170.10.156.0/24",
"170.10.157.0/24"
]
}
}
],
"domains_extracted": [
"myspace.com",
"_netblocks.mimecast.com",
"eu._netblocks.mimecast.com",
"us._netblocks.mimecast.com",
"za._netblocks.mimecast.com",
"de._netblocks.mimecast.com",
"au._netblocks.mimecast.com",
"ca._netblocks.mimecast.com",
"usb._netblocks.mimecast.com"
],
"authorized_ips": {
"ipv4": [
"63.208.226.34",
"204.16.32.0/22",
"67.134.143.0/24",
"216.205.243.0/24",
"34.85.156.5/32",
"35.245.108.108/32",
"34.86.129.193/32",
"34.86.134.94/32",
"34.85.222.234/32",
"34.86.176.234/32",
"34.86.125.212/32",
"34.85.224.60/32",
"34.86.160.49/32",
"35.245.64.166/32",
"35.188.226.11/32",
"34.86.208.228/32",
"34.85.216.144/32",
"35.221.22.153/32",
"34.86.137.108/32",
"34.86.51.35/32",
"34.150.221.40/32",
"34.85.216.70/32",
"34.86.37.191/32",
"34.85.214.215/32",
"35.236.234.82/32",
"34.86.161.241/32",
"216.32.181.16",
"216.178.32.0/20",
"168.235.224.0/24",
"195.130.217.0/24",
"91.220.42.0/24",
"146.101.78.0/24",
"207.82.80.0/24",
"213.167.81.0/25",
"193.7.207.0/25",
"213.167.75.0/25",
"185.58.85.0/24",
"185.58.86.0/24",
"193.7.206.0/25",
"147.28.36.0/24",
"207.211.31.0/25",
"205.139.110.0/24",
"216.205.24.0/24",
"170.10.129.0/24",
"63.128.21.0/24",
"170.10.133.0/24",
"185.58.84.93/32",
"207.211.41.113/32",
"207.211.30.64/26",
"207.211.30.128/25",
"216.145.221.0/24",
"170.10.128.0/24",
"170.10.132.56/29",
"170.10.132.64/29",
"41.74.192.0/22",
"41.74.200.0/23",
"41.74.196.0/22",
"41.74.204.0/23",
"41.74.206.0/24",
"51.163.158.0/24",
"194.104.109.0/24",
"194.104.111.0/24",
"194.104.110.21/32",
"194.104.110.240/28",
"62.140.10.21/32",
"62.140.7.0/24",
"194.104.108.240/29",
"194.104.108.21/32",
"51.163.159.0/24",
"103.13.69.0/24",
"124.47.150.0/24",
"124.47.189.0/24",
"103.96.23.0/24",
"103.96.21.0/24",
"180.189.28.0/24",
"216.145.217.0/24",
"103.96.22.96/28",
"103.96.22.22/32",
"103.96.20.22/32",
"103.96.20.96/28",
"170.10.145.0/24",
"170.10.147.0/24",
"170.10.144.126/32",
"170.10.146.126/32",
"170.10.144.240/29",
"170.10.146.240/29",
"216.145.216.0/24",
"170.10.151.0/24",
"170.10.153.0/24",
"170.10.150.240/29",
"170.10.152.240/29",
"170.10.156.0/24",
"170.10.157.0/24"
],
"ipv6": []
},
"issues_found": [],
"spf_valid": true,
"has_issues": false,
"macros_found": false,
"ip_pass": false,
"elapsed_ms": 431,
"all_qualifier": "fail",
"risk_score": 5,
"risk_level": "low"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
host | string | "myspace.com" | The domain name being validated |
has_spf_record | boolean | true | Whether the domain has SPF record |
dns_lookups_numPremium | number | 9 | Total number of DNS lookups performed |
spf_record | string | "v=spf1 mx ip4:63.208.226.34 ip4:204.16.32.0/22 ip4:67.134.143.0/24 ip4:216.205.243.0/24 ip4:34.85.156.5/32 ip4:35.245.108.108/32 ip4:34.86.… | The complete SPF record string |
spf_records_listPremium | array[9] | List of SPF records with detailed parsing | |
originPremium | string | "myspace.com" | Domain origin of SPF record |
recordPremium | string | "v=spf1 mx ip4:63.208.226.34 ip4:204.16.32.0/22 ip4:67.134.143.0/24 ip4:216.205.243.0/24 ip4:34.85.156.5/32 ip4:35.245.108.108/32 ip4:34.86.… | Full SPF record content |
chars_numPremium | number | 637 | Character count of SPF record |
use_macroPremium | boolean | false | Whether record uses macros |
domainsPremium | array | [_netblocks.mimecast.com] | Domains referenced in SPF record |
authorized_ipsPremium | object | {...} | All IP addresses authorized by SPF |
ipv4Premium | array | [63.208.226.34, ...] | IPv4 addresses authorized to send mail |
domains_extractedPremium | array | [myspace.com, ...] | All domains found in SPF chain |
authorized_ipsPremium | object | {...} | All IP addresses authorized by SPF |
ipv4Premium | array | [63.208.226.34, ...] | All IPv4 addresses authorized by SPF |
ipv6Premium | array | [] | All IPv6 addresses authorized by SPF |
issues_foundPremium | array | [] | List of SPF validation issues |
spf_valid | boolean | true | Whether SPF record is valid |
has_issues | boolean | false | Whether validation found issues |
macros_foundPremium | boolean | false | Whether SPF record uses macros |
ip_pass | boolean | false | Whether IP passes SPF check |
elapsed_msPremium | number | 431 | Validation processing time in milliseconds |
all_qualifier | string | "fail" | The qualifier on the SPF 'all' mechanism: fail (-all, strict), softfail (~all), neutral (?all) or pass (+all, authorizes any sender). Null when the record has no all mechanism (e.g. defers via redirect) |
risk_scorePremium | number | 5 | Composite 0-100 email-spoofing risk based on the SPF enforcement qualifier and DNS-lookup limit — higher means the domain is more easily spoofed (no SPF or +all scores high; -all scores low) |
risk_levelPremium | string | "low" | Risk band derived from the score: low, medium or high |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | SPF Validator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/spfvalidator
No SDK to install — this is a plain HTTPS call to /v1/spfvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/spfvalidator" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/spfvalidator
Install the Node.js SDK, then call the SPF Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/spfvalidatorconst res = await fetch("https://api.apiverve.com/v1/spfvalidator", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/spfvalidator
Install the Python SDK, then call the SPF Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-spfvalidatorimport requests
res = requests.get(
"https://api.apiverve.com/v1/spfvalidator",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/spfvalidator
Install the C# / .NET SDK, then call the SPF Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.SPFValidatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/spfvalidator");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/spfvalidator
No SDK to install — this is a plain HTTPS call to /v1/spfvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/spfvalidator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/spfvalidator
No SDK to install — this is a plain HTTPS call to /v1/spfvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/spfvalidator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/spfvalidator
No SDK to install — this is a plain HTTPS call to /v1/spfvalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/spfvalidator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive SPF Validator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — SPF Validator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the SPF Validator API.
Domain Data
- BIMI Record Validator
- DKIM Validator
- DMARC Validator
- DNS Lookup
- DNS Propagation Checker
- DNSSEC Checker
- Domain Availability
- Domain Expiration
- Fully Qualified Domain
- MX Lookup
- Reverse DNS Lookup
- SPF Validator
- SSL Certificate Checker
- Subdomain Finder
- URL Lookup
- URL Title
- URL Unshortener
- WHOIS Lookup
Related articles
All articles →
7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read
DNS Lookups: A Developer's Debugging GuideDNS problems cause connection failures and email issues. Learn how to use DNS lookups to diagnose problems faster.Read
WHOIS Data: Domain Intelligence for Business and SecurityWHOIS data reveals domain ownership, age, and infrastructure. Use it for lead qualification, research, and fraud detection.Read