vulnfeed-api.novadyne.ai/vulnscan/cve/CVE-2021-44228
1.Catalog declaration
| Resource URL | https://vulnfeed-api.novadyne.ai/vulnscan/cve/CVE-2021-44228 |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xbecce6dd106cfa910f78fea188b2fcceb73bdd0f |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 7 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 22:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 426 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 887 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 569 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 470 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 224 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 459 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 2152 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2128 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 72 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-19 18:002026-09-19 18:00 UTC | settled (nonce-bound)tx from our index | 200 | 0x2ea6e2ab…66a1 | 1266 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 12:092026-09-09 12:09 UTC | settled (nonce-bound)tx from our index | 200 | 0xc306f61d…d383 | 1195 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-28 12:182026-08-28 12:18 UTC | settled (amount + payee)tx from our index | 200 | 0x570ab774…1e15 | 955 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-21 08:332026-08-21 08:33 UTC | settled (amount + payee)tx from our index | 200 | 0xca752cff…f72e | 837 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/8cbaaa9d-db6f-4672-a64a-7eedae554119)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
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. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.