spf record audit derived
api.zfinia.comCommunicationsderived
POST https://api.zfinia.com/x402/v1/spf-record-audit
passabsent from every registry#7 by calls of 15 on this host
0.2 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-04 21:22 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 50% / 50%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:40 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.2 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 2 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
api.zfinia.com lists 15 endpoints; spf record audit is tied 7th by calls with 9 others.
The request to spf record audit is a json body with the fields domain, records and assume_lookups_per_include.
A response from spf record audit, as declared, includes terms, valid, domain, limits, passed, record and 2 others.
spf record audit drew a single call from a single payer in the trailing 30 days.
The last call to spf record audit came 9 days before the snapshot, 2026-10-04.
Per call, spf record audit declares 0.2 USDC on Base.
spf record audit takes 4% of the calls counted across api.zfinia.com.
api.zfinia.com serves spf record audit, a POST endpoint that TOLL places in communications, listed in neither registry at the last pull.
spf record audit answered the sweep of 2026-10-04 with a valid 402, passing 1 of 2 sweeps since 2026-10-04.
Closest in price to spf record audit within communications: tools x timeline at twitr.sh and startup domain check at api.strale.io.
spf record audit is near the top of prices in communications; 97% of comparable listings are cheaper.
The wallet paid by spf record audit is the payee of 179 endpoints across 5 hosts.
The seller's tags on spf record audit are spf, email authentication, domain trust and dns.
spf record audit was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-04 21:22 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 14:11 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 14:11 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:48 UTC | fail | 1 | new-after-daily-2026-10-04 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 08:40 UTC · method
The input and output block
{
"input": {
"body": {
"domain": "example.test",
"records": [
"v=spf1 include:_spf.vendor-a.test include:_spf.vendor-b.test include:_spf.vendor-c.test include:spf.vendor-d.test include:mail.vendor-e.test a mx ptr exists:%{i}._auth.example.test include:_spf.vendor-f.test include:_spf.vendor-g.test ~all include:late.vendor.test",
"v=spf1 include:_spf.legacy.test ~all",
"google-site-verification=abc123"
],
"assume_lookups_per_include": 1
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"terms": [
{
"term": "include:_spf.vendor-a.test",
"lookups": 1,
"mechanism": "include",
"qualifier": "+"
},
{
"term": "include:_spf.vendor-b.test",
"lookups": 1,
"mechanism": "include",
"qualifier": "+"
},
{
"term": "include:_spf.vendor-c.test",
"lookups": 1,
"mechanism": "include",
"qualifier": "+"
}
],
"valid": false,
"domain": "example.test",
"limits": {
"maxRecords": 2000,
"maxFindings": 500,
"maxHeaderBytes": 131072,
"maxIncludeTree": 200,
"spfLookupLimit": 10,
"maxRecordLength": 4096,
"spfVoidLookupLimit": 2
},
"passed": false,
"record": "v=spf1 include:_spf.vendor-a.test include:_spf.vendor-b.test include:_spf.vendor-c.test include:spf.vendor-d.test include:mail.vendor-e.test a mx ptr exists:%{i}._auth.example.test include:_spf.vendor...",
"complete": false,
"findings": [
{
"code": "SEVERAL_SPF_RECORDS",
"detail": "2 records begin with v=spf1. More than one is a permanent error, and most receivers then treat the domain as having no SPF at all. Adding a vendor means merging into the one record, not adding another..."
},
{
"code": "RECORD_LONGER_THAN_ONE_STRING",
"detail": "The record is 264 characters. A single DNS character string holds 255, so this must be published as several strings inside one record, which is not the same as several records."
},
{
"code": "PTR_MECHANISM_USED",
"detail": "The record uses ptr, which the specification says should not be published: it is slow, it costs a lookup, and some receivers ignore it entirely."
}
],
"request_id": "example-request",
"service_id": "spf_record_audit",
"assumptions": [
"Nothing resolves DNS. The records are supplied, which keeps the egress surface at zero and means an arbitrary domain can be audited without this service holding an allowlist for it.",
"An include is counted at the stated cost per include, and the included record is not read, so the lookup count here is a floor rather than the true total. That is said rather than presented as exact.",
"An unrecognised term is reported rather than skipped, because an unrecognised mechanism is itself a permanent error and skipping it would report a broken record as sound."
],
"limitations": [
"The records supplied. Whether they are actually published, whether an include resolves, and what any particular receiver does are outside this.",
"valid is true only when the record parsed, stayed inside the lookup limit, and nothing was left unexamined."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"lookup_limit": 10,
"not_examined": [
"RECORD_NOT_SPF: A record was supplied that does not begin with v=spf1 and was not evaluated: google-site-verification=abc123",
"INCLUDE_TREE_NOT_EXPANDED: Each include and redirect was counted as 1 lookup(s) because the included records were not supplied. The real total is at least this and usually more, so the count here is a..."
],
"record_count": 3,
"finding_count": 5,
"service_version": "1.0.0",
"findings_by_code": {
"TERM_AFTER_ALL": 1,
"PTR_MECHANISM_USED": 1,
"SEVERAL_SPF_RECORDS": 1,
"LOOKUP_LIMIT_EXCEEDED": 1,
"RECORD_LONGER_THAN_ONE_STRING": 1
},
"minimum_dns_lookups": 12,
"lookups_assumed_per_include": 1
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "spf record audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-spf-record-audit-caa7e1. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-spf-record-audit-caa7e1-2026-10-13,
author = {TOLL},
title = {spf record audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-spf-record-audit-caa7e1}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.