risk data for machine payments
Endpoint
?
767-2676.com/v1/time
767-2676.com · not enough data yet · recomputed 23m ago
Signed bearer temporal evidence for cross-node execution-window grounding and audit
NEW_UNKNOWN
First seen
11h ago
Probes stored
2
Payers
2
On-chain volume
$0.01
No score yet: there are not enough observations. We do not assign a low
grade for missing data — a new endpoint would otherwise look dead. The
prepay verdict
in that case is warn: unknown is a risk, not a clean bill of health.Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 4h ago | 402 | 183 ms | exact eip155:8453 |
0x5f5a…3cb8 | 0.001000 | clean |
| 11h ago | 402 | 958 ms | exact eip155:8453 |
0x5f5a…3cb8 | 0.001000 | clean |
Settlements to this wallet
| When | Payer | Amount | Facilitator | Transaction |
|---|---|---|---|---|
| 3d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x1e7637…fb42 |
| 3d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x6300ad…9c26 |
| 3d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x7a15b9…eea0 |
| 3d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x547cbf…ea8b |
| 3d ago | 0x54e1…f4e0 | $0.00100 | not in registry | 0x52f5aa…61c1 |
| 4d ago | 0xa119…1b64 | $0.00100 | not in registry | 0xd52772…657c |
| 5d ago | 0x54e1…f4e0 | $0.00100 | not in registry | 0xe3ac42…c513 |
| 5d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x7ee9f7…279d |
| 5d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x8b6ba8…c489 |
| 5d ago | 0xa119…1b64 | $0.00100 | not in registry | 0xf150a8…2018 |
| 5d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x68337f…34ef |
| 5d ago | 0xa119…1b64 | $0.00100 | not in registry | 0x960ddc…5040 |
Reference
| URL | https://767-2676.com/v1/time |
| Sources | bazaar |
| Recipient per catalogue | 0x5f5a631e975183d084f60d7121e967b30ec83cb8 |
| 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.