Directory / dns.halowerk.com
dns.halowerk.com/domain/articles/mx-united-domains working
https://dns.halowerk.com/domain/articles/mx-united-domains
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
- 7 min ago · 15 ms · HTTP 402
- Detail
- 402 with valid terms
Reliability
- Uptime 24 h
- 100.0% (37 checks)
- Uptime 7 days
- 100.0% (247 checks)
- Uptime, 10 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
- 11,022 payments from 47 wallets, $36.65USDC on Base into this address since 2026-10-16; alalanet's own test wallet excluded
- Repeat payers
- 24 paid on two or more days
- Largest payer
- 61.3% of the payments
- Independent payers
- 9 of 47 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 37 payers are not counted
This address also receives for 115 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-15 00:14 UTC | 413996aa…c5828d daily summary | 748606 |
| 2026-11-14 00:13 UTC | b9d03f5e…7a5274 daily summary | 672502 |
| 2026-11-13 00:11 UTC | 79192c52…c4d821 daily summary | 595380 |
| 2026-11-12 00:14 UTC | 69941c36…844625 daily summary | 517331 |
| 2026-11-11 00:14 UTC | 7b1e6f4f…18da29 daily summary | 437085 |
| 2026-11-10 00:13 UTC | 2f11db63…955393 daily summary | 353930 |
| 2026-11-09 00:11 UTC | a87a6198…5eb050 daily summary | 263011 |
| 2026-11-08 00:09 UTC | 0cc846ab…95d06f daily summary | 184416 |
| 2026-11-07 00:12 UTC | 489ddce7…0159f3 daily summary | 105050 |
| 2026-11-06 00:09 UTC | 90e3742c…6e8454 daily summary | 17732 |
Verify any statement offline: how.
For agents and owners
JSON: https://alalanet.com/v1/services/btc363h2yhl6qqqk
Badge:
<a href="https://alalanet.com/s/btc363h2yhl6qqqk"><img src="https://alalanet.com/badge/btc363h2yhl6qqqk" alt="alalanet status"></a>
Own this service? Claim it (free). Do not want it checked? See the prober page.