Directory / dns.halowerk.com
dns.halowerk.com/domain/articles/ns-cloudflare working
https://dns.halowerk.com/domain/articles/ns-cloudflare
Before you pay
- Advice
ok- Protocol
- x402 · http · POST
- Asks for
- 0.009 USDC on base
- Catalogue says
- 0.009 USDC
- Pays to
0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E- Last check
- 36 min ago · 15 ms · HTTP 402
- Detail
- 402 with valid terms
Reliability
- Uptime 24 h
- 100.0% (35 checks)
- Uptime 7 days
- 100.0% (258 checks)
- Uptime, 13 days observed
- 100.0% (signed daily)
- Listed by
- x402-bazaar
- First seen by alalanet
- 2026-11-05 22:12 UTC
Trust Score
62 of 95
Open formula: /trust. Recomputed once a day from what alalanet observed and its sources publish; nothing here can be bought.
shared_pay_to— the same receiving address serves 50 or more hosts (−5).single_payer_demand— at most one paying wallet counts — on chain, after the funding check when one was made, or in the catalogue's own figures; often it is the seller's own (paid demand counts 2 at most).
Payments
- Read on chain by alalanet
- 13,093 payments from 58 wallets, $47.19USDC on Base into this address since 2026-10-19; alalanet's own test wallet excluded
- Repeat payers
- 27 paid on two or more days
- Largest payer
- 66.1% of the payments
- Independent payers
- 9 of 58 countedalalanet read the wallets of the 10 largest payers: 1 funded by the seller, not counted; 0 joined to another payer (funded by it, or by the same address within 72 hours before both paid); 6 first funded within 72 hours before paying; the other 48 payers are not counted
This address also receives for 123 other hosts; the payments above are for all of them.
This listing was first seen on 2026-11-05; payments before that day may be missing, so the figures are a lower bound.
- Catalogue says
- 1 calls from 1 payer in 30 daysthe catalogue's own counter (x402 Bazaar), not checked by alalanet
Description (from the catalogue, unverified)
Requires an unauthenticated caller-owned baseline; returns real current NS/MX records, added/removed sets and tri-state target-provider transition. Current DNS comes from one bounded native recursive-resolver query; existing Dossier provides context. Resolver caching may apply; no account ownership or global migration-completion claim. Existing provider patterns are reused without new invented attribution. At most50records,domain253chars,9sbudget; DNSsubquery2s/oneattempt. Unknown provider remai
Signed history
| When | Statement | Log index |
|---|---|---|
| 2026-11-18 00:14 UTC | 0556fe7d…3a7976 daily summary | 1001667 |
| 2026-11-17 00:18 UTC | 06033725…6d2d60 daily summary | 922072 |
| 2026-11-16 00:15 UTC | fc4dba78…d1e21f daily summary | 842039 |
| 2026-11-15 00:16 UTC | af6033d4…676f36 daily summary | 765812 |
| 2026-11-14 00:16 UTC | 5f7609a8…93dbda daily summary | 689673 |
| 2026-11-13 00:13 UTC | 90c2f330…dfef58 daily summary | 612369 |
| 2026-11-12 00:16 UTC | d5cf78c5…01ed29 daily summary | 534110 |
| 2026-11-11 00:16 UTC | 1a94d4ed…ec8a5a daily summary | 453726 |
| 2026-11-10 00:16 UTC | 2ddd04c7…48ce27 daily summary | 370857 |
| 2026-11-09 00:14 UTC | 380bdedf…3b3b0c daily summary | 279775 |
Verify any statement offline: how.
For agents and owners
JSON: https://alalanet.com/v1/services/jmzcgqghtqg4yros
Badge:
<a href="https://alalanet.com/s/jmzcgqghtqg4yros"><img src="https://alalanet.com/badge/jmzcgqghtqg4yros" alt="alalanet status"></a>
Own this service? Claim it (free). Do not want it checked? See the prober page.