email security derived
tools.halowerk.comCommunicationsderived
POST https://tools.halowerk.com/v1/email/security
passlisted in Coinbase#7 by calls of 37 on this host
0.002 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
- 3
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-10-08 06:07 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.002 USDC
- Networks
- 1
How has the volume on this endpoint moved?
Among the 37 endpoints on tools.halowerk.com, email security is tied 7th by calls with 28 others.
The request to email security is a json body with the fields domain and dkim_selectors.
email security returns json; the example shows score, checks, domain, findings, checked_at and spoofing_risk.
The registry's counters give email security 3 calls and 3 unique payers over 30 days, every call from a different payer.
email security was last called 5 days before the snapshot.
Per call, email security declares 0.002 USDC on Base.
3% of the host's counted calls go to it.
email security is a POST endpoint at tools.halowerk.com, listed in the Coinbase registry and filed by TOLL under communications.
email security answered the sweep of 2026-10-21 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to email security within communications: web fetch at glim.sh and trending altcoins at x402.ottoai.services.
email security is among the cheapest in communications; 6% of comparable listings ask less.
Across communications, 935 endpoints carry counters and email security out-counts 67% of them.
The payee wallet is shared by 1,941 listings across 79 hosts.
The seller's tags on email security are x402, agent-tools, security and mail_security.
It disappeared from the registry on 2026-09-15 and returned on 2026-10-07.
The price of email security is declared by 31 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.002 USDC | exact | 0x2880Ed…1C4E5E |
the checks, as of 2026-10-21 08:02 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-21 08:02 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 08:24 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 05:58 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 08:11 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 18:12 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 04:26 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 06:00 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 04:24 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 08:50 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 06:14 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 04:37 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 09:54 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 04:39 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 06:17 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 06:06 UTC | pass | 0 | daily-2026-10-07 |
| 2026-09-15 04:04 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:03 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:02 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:17 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 09:44 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- 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-08 06:07 UTC · method · live
The input and output block
{
"input": {
"body": {
"domain": "example.com",
"dkim_selectors": [
"default",
"google",
"selector1"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"score": 41,
"checks": {
"spf": {
"value": {
"record": "v=spf1 include:_spf.google.com ~all",
"dns_lookups": 4,
"all_mechanism": "~all"
},
"detail": {
"de": "SPF endet auf \"~all\" (softfail).",
"en": "SPF ends in \"~all\" (softfail)."
},
"status": "schwach"
},
"dmarc": {
"value": {
"record": null
},
"detail": {
"de": "Kein DMARC-Datensatz.",
"en": "No DMARC record."
},
"status": "fehlt"
}
},
"domain": "example.com",
"findings": [
{
"fix": "_dmarc.example.com. 3600 IN TXT \"v=DMARC1; p=none; rua=mailto:dmarc@example.com; adkim=r; aspf=r; pct=100\"",
"title": {
"de": "DMARC fehlt",
"en": "DMARC missing"
},
"severity": "kritisch",
"why_it_matters": {
"de": "Ohne DMARC entscheidet jeder Empfänger selbst, was mit einer gefälschten Mail geschieht.",
"en": "Without DMARC every receiver decides for itself what happens to a forged message."
}
}
],
"checked_at": "2026-08-06T12:00:00.000Z",
"spoofing_risk": "hoch"
}
}
}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, "email security on tools.halowerk.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/tools-halowerk-com-v1-email-security-188546/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-tools-halowerk-com-v1-email-security-188546-2026-10-13T14-08Z,
author = {TOLL},
title = {email security on tools.halowerk.com},
howpublished = {\url{https://tollindex.com/e/tools-halowerk-com-v1-email-security-188546/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.