43-135-4-66.sslip.io/v1/filings/risk-scan
1.Catalog declaration
| Resource URL | https://43-135-4-66.sslip.io/v1/filings/risk-scan |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x7aac1cce7113306c7af59f82637d0a38b3e5c6b0 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-09-11 01:03 UTC / 2026-10-29 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-28 04:40 UTC | POST | pass | 402 | 808 ms | — |
| 2026-10-26 06:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-24 13:40 UTC | POST | pass | 402 | 1790 ms | — |
| 2026-10-22 16:40 UTC | POST | pass | 402 | 881 ms | — |
| 2026-10-21 04:40 UTC | POST | pass | 402 | 966 ms | — |
| 2026-10-19 16:40 UTC | POST | pass | 402 | 1814 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 852 ms | — |
| 2026-10-16 15:40 UTC | POST | pass | 402 | 2700 ms | — |
| 2026-10-15 03:40 UTC | POST | pass | 402 | 899 ms | — |
| 2026-10-13 21:40 UTC | POST | pass | 402 | 742 ms | — |
| 2026-10-12 15:40 UTC | POST | pass | 402 | 845 ms | — |
| 2026-10-11 15:40 UTC | POST | pass | 402 | 2927 ms | — |
| 2026-10-10 15:40 UTC | POST | pass | 402 | 826 ms | — |
| 2026-10-09 15:40 UTC | POST | pass | 402 | 795 ms | — |
| 2026-10-08 13:40 UTC | POST | pass | 402 | 866 ms | — |
| 2026-10-01 10:30 UTC | POST | pass | 402 | 754 ms | — |
| 2026-09-25 10:31 UTC | POST | pass | 402 | 880 ms | — |
| 2026-09-21 11:24 UTC | POST | pass | 402 | 857 ms | — |
| 2026-09-17 16:19 UTC | POST | pass | 402 | 779 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 736 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 871 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight. If it was right, it stands. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.