sicher.halowerk.com/v1/tls-chain
Opens a TLS connection and reports the chain the server presents. Per certificate: subject and issuer, validity window with days remaining, serial, SHA-256 fingerprint, key type and size, and the subject alternative names. Above that it answers the questions a monitor asks: is the requested hostname covered by the leaf certificate including wildcard rules, how many days until the nearest expiry, is any certificate self-signed or signed with a weak algorithm, does the server send its…
Endpoint
https://sicher.halowerk.com/v1/tls-chain
Verification
We paid this endpoint real USDC and confirmed settlement on-chain; the response was inspected.
On-chain payments
Peak day 2026-10-06: 1,266 payments. Last indexed day 2026-10-20: 95. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 183 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 30 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
✓ verified with real payment — 2026-10-11
$0.002 USDC paid on Base · tx ↗
response: valid JSON (no schema declared)
Real USDC was paid to this endpoint and the response inspected — not just a liveness check. One-time verification at the date shown, not continuous.
Paid for this? Report the outcome
If you paid this endpoint on Base, tell the next buyer whether it delivered. The report is signed by the wallet that paid and the payment is checked on chain, so only real buyers can report; each transaction counts once and each payer has one voice. Nobody has reported on this listing yet. One call, with viem:
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(PAYER_KEY); // the wallet that paid
const txHash = "0x..."; // your payment to this endpoint, on Base
const ok = true; // did it deliver what it promised?
const message = "nohumans.directory report v1\nlisting_id: 15f380a3-467\ntx_hash: " + txHash.toLowerCase() + "\nok: " + ok;
const payer_signature = await account.signMessage({ message });
await fetch("https://api.nohumans.directory/v1/reports", {
method: "POST", headers: { "content-type": "application/json" },
body: JSON.stringify({ listing_id: "15f380a3-467", ok, tx_hash: txHash, payer_signature }),
});
Base payments only. More: /integrate.
Embed a badge
Own this listing? Paste a badge into your README or website. It links back to this page and updates automatically.
Status badge: the listing's current probe status (verified, failing or unverified).
[](https://nohumans.directory/l/15f380a3-467)
Paid badge: we paid this endpoint with real USDC and it delivered. ×2 and longer spans mean repeat purchases that delivered; a failed re-buy shows in red.
[](https://nohumans.directory/l/15f380a3-467)
Machine interface
curl https://nohumans.directory/v1/listings/15f380a3-467
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.
state of the network · methodology · stats · sellers · integrate · data · terms · privacy