spf check derived
emailauth.openverbs.comCommunicationsderived
POST https://emailauth.openverbs.com/v1/spf-check
passlisted in Coinbase#1 by calls of 4 on this host
0.004 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-06 16:58 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.004 USDC
- Networks
- 1
How has the volume on this endpoint moved?
spf check, a POST endpoint on emailauth.openverbs.com, appears in the Coinbase registry; TOLL's taxonomy puts it in communications.
On Base, spf check asks 0.004 USDC per call.
Requests carry a json body with the fields ip and record.
spf check declares nothing about its output; validate flags that as advisory, not a verdict.
spf check answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-09-11.
spf check shares emailauth.openverbs.com with 3 other listed endpoints and is tied 1st by calls with 3 others.
spf check takes 25% of the calls counted across emailauth.openverbs.com.
In the trailing 30 days: one call, one payer.
spf check was last called 7 days before the snapshot.
Closest in price to spf check within communications: users tweets at glim.sh and tools validate email at api.qocgpiywhm.com.
spf check is priced above 14% of comparable listings in communications.
The payee wallet is shared by 411 listings across 91 hosts.
The seller's tags on spf check are check spf ip, evaluate spf record, spf ip validation and spf sender check.
spf check dropped out of the registry at the pull of 2026-10-06 and was listed again on 2026-10-07.
The price of spf check is declared by 35 other listings in communications too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.004 USDC | exact | 0xb3f4de…C2194A |
the checks, as of 2026-10-30 07:10 UTC · method · pinnableendpoint answered HTTP 402
bazaar.info.output· advisory, does not affect the verdict · output metadata is present (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-30 07:10 UTC | pass | 1 | daily-2026-10-30 |
| 2026-10-29 06:52 UTC | pass | 1 | daily-2026-10-29 |
| 2026-10-28 07:14 UTC | pass | 1 | daily-2026-10-28 |
| 2026-10-27 07:05 UTC | pass | 1 | daily-2026-10-27 |
| 2026-10-26 12:24 UTC | pass | 1 | daily-2026-10-26 |
| 2026-10-24 21:47 UTC | pass | 1 | daily-2026-10-24 |
| 2026-10-23 07:02 UTC | pass | 1 | daily-2026-10-23 |
| 2026-10-22 05:18 UTC | pass | 1 | daily-2026-10-22 |
| 2026-10-21 08:57 UTC | pass | 1 | daily-2026-10-21 |
| 2026-10-20 09:09 UTC | pass | 1 | daily-2026-10-20 |
| 2026-10-19 06:45 UTC | pass | 1 | daily-2026-10-19 |
| 2026-10-18 08:55 UTC | pass | 1 | daily-2026-10-18 |
| 2026-10-17 18:58 UTC | pass | 1 | daily-2026-10-17 |
| 2026-10-16 05:09 UTC | pass | 1 | daily-2026-10-16 |
| 2026-10-15 06:46 UTC | pass | 1 | daily-2026-10-15 |
| 2026-10-14 05:04 UTC | pass | 1 | daily-2026-10-14 |
| 2026-10-13 09:35 UTC | pass | 1 | daily-2026-10-13 |
| 2026-10-12 07:00 UTC | pass | 1 | daily-2026-10-12 |
| 2026-10-11 05:22 UTC | pass | 1 | daily-2026-10-11 |
| 2026-10-10 13:38 UTC | pass | 1 | daily-2026-10-10 |
| 2026-10-09 05:38 UTC | pass | 1 | daily-2026-10-09 |
| 2026-10-08 07:21 UTC | pass | 1 | daily-2026-10-08 |
| 2026-10-07 06:32 UTC | pass | 1 | daily-2026-10-07 |
| 2026-10-06 07:22 UTC | pass | 1 | daily-2026-10-06 |
| 2026-10-05 06:52 UTC | pass | 1 | daily-2026-10-05 |
| 2026-10-04 09:40 UTC | pass | 1 | daily-2026-10-04 |
| 2026-10-03 04:43 UTC | pass | 1 | daily-2026-10-03 |
| 2026-10-02 13:56 UTC | pass | 1 | daily-2026-10-02 |
| 2026-10-01 07:02 UTC | pass | 1 | daily-2026-10-01 |
| 2026-09-30 06:20 UTC | pass | 1 | daily-2026-09-30 |
| 2026-09-29 18:40 UTC | pass | 1 | daily-2026-09-29 |
| 2026-09-28 04:31 UTC | pass | 1 | daily-2026-09-28 |
| 2026-09-25 20:14 UTC | pass | 1 | daily-2026-09-25 |
| 2026-09-23 05:53 UTC | pass | 1 | daily-2026-09-23 |
| 2026-09-22 06:03 UTC | pass | 1 | daily-2026-09-22 |
| 2026-09-21 06:26 UTC | pass | 1 | daily-2026-09-21 |
| 2026-09-20 19:05 UTC | pass | 1 | daily-2026-09-20 |
| 2026-09-19 04:27 UTC | pass | 1 | daily-2026-09-19 |
| 2026-09-18 10:16 UTC | pass | 1 | daily-2026-09-18 |
| 2026-09-17 04:25 UTC | pass | 1 | daily-2026-09-17 |
| 2026-09-16 04:25 UTC | pass | 1 | daily-2026-09-16 |
| 2026-09-15 04:23 UTC | pass | 1 | daily-2026-09-15 |
| 2026-09-14 04:20 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 04:19 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 06:35 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 10:05 UTC | pass | 1 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- absent from Coinbase at this pull
- back in Coinbase
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-06 16:58 UTC · method · live
The input and output block
{
"input": {
"body": {
"ip": "192.0.2.10",
"record": "v=spf1 ip4:192.0.2.0/24 -all"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": null
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "spf check on emailauth.openverbs.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/emailauth-openverbs-com-v1-spf-check-3399de/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-emailauth-openverbs-com-v1-spf-check-3399de-2026-10-13T14-08Z,
author = {TOLL},
title = {spf check on emailauth.openverbs.com},
howpublished = {\url{https://tollindex.com/e/emailauth-openverbs-com-v1-spf-check-3399de/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.