risk data for machine payments
Endpoint
api.webbersites.com/api/ping
Cheapest liveness ping: ONE request to any public URL — is anything answering, and how fast? Returns up/down, HTTP status, and latency in ms. Any HTTP response below 500 counts as up; redirects are reported, not followed. High-frequency monitoring loops belong here; step up to /api/uptime for redirect following and headers, /api/uptime/report for the full timing/TLS/CDN report.
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 6h ago | 402 | 101 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.001000 | clean |
| 4d ago | 402 | 156 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.001000 | clean |
| 4d ago | 402 | 141 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.001000 | clean |
Reference
| URL | https://api.webbersites.com/api/ping |
| Sources | well-known |
| Recipient per catalogue | 0xdd5fcEa81CA6f1EB39FEd5B973DE794293B81ba6 |
| Price per catalogue | 0.001000 |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.