Directory / sicher.halowerk.com
sicher.halowerk.com/v1/oss-openssl-csr-self-signature-audit working
https://sicher.halowerk.com/v1/oss-openssl-csr-self-signature-audit
Before you pay
- Advice
ok- Protocol
- x402 · http · POST
- Asks for
- 0.002 USDC on base
- Catalogue says
- 0.002 USDC
- Pays to
0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E- Last check
- 24 min ago · 15 ms · HTTP 402
- Detail
- 402 with valid terms
Reliability
- Uptime 24 h
- 100.0% (46 checks)
- Uptime 7 days
- 99.7% (320 checks)
- Uptime, 10 days observed
- 99.8% (signed daily)
- Listed by
- x402-bazaar
- First seen by alalanet
- 2026-11-05 22:10 UTC
Trust Score
63 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).
Payments
- Read on chain by alalanet
- 11,008 payments from 47 wallets, $36.62USDC 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.4% 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
- 4 calls from 4 payers in 30 daysthe catalogue's own counter (x402 Bazaar), not checked by alalanet
Description (from the catalogue, unverified)
Runs the pinned OpenSSL build against a submitted certificate request and answers two questions a registration authority has to settle before it signs anything: does the request carry a valid self-signature over its own body, and what exactly is being requested. The reply names the subject, the public key parameters and every requested extension as OpenSSL parses them, so a policy check compares against the parsed request rather than the text an applicant supplied.
Signed history
| When | Statement | Log index |
|---|---|---|
| 2026-11-15 00:20 UTC | fd1f5db3…38e889 daily summary | 799985 |
| 2026-11-14 00:20 UTC | d142fa9d…0dfdb0 daily summary | 723739 |
| 2026-11-13 00:18 UTC | 5cdf41a2…27f346 daily summary | 646013 |
| 2026-11-12 00:20 UTC | 0befb5da…4a3acf daily summary | 567430 |
| 2026-11-11 00:20 UTC | 3d6dd79e…8f65db daily summary | 486780 |
| 2026-11-10 00:20 UTC | 527056ae…7ae1c2 daily summary | 404613 |
| 2026-11-09 15:58 UTC | 49751908…48f0db status change | 325224 |
| 2026-11-09 15:58 UTC | 137e172c…502d3a status change | 325210 |
| 2026-11-09 00:18 UTC | 8276a044…95aa35 daily summary | 313079 |
| 2026-11-08 00:16 UTC | 44a2025c…1a3f2a daily summary | 234992 |
Verify any statement offline: how.
For agents and owners
JSON: https://alalanet.com/v1/services/z4fzlpipjjj7sqsv
Badge:
<a href="https://alalanet.com/s/z4fzlpipjjj7sqsv"><img src="https://alalanet.com/badge/z4fzlpipjjj7sqsv" alt="alalanet status"></a>
Own this service? Claim it (free). Do not want it checked? See the prober page.