← Back to reports

Conformance report
gate402.app

Checked: 2026-09-28T00:15:18.366Z

Resource: POST /v1/proxy

Result: 2/11 passed

Fingerprint: sha256:eab94b2da21ae49c21fb83a9e66dae9b8218dac37ba101af8bcd5cfaa046feb0

Open seller site ↗

Individual checks

CheckHTTPGradeReason
challenge_present
Does an unpaid request answer with a valid 402 challenge?		402passedValid HTTP 402 challenge.
malformed_signature
Is an unreadable payment header refused rather than answered with a 5xx?		402passedRefused with HTTP 402.
wrong_recipient
Is a payment to a different recipient refused?		500failedServer error 500 instead of a refusal.
wrong_asset
Is a token other than the one demanded refused?		500failedServer error 500 instead of a refusal.
underpayment
Is an amount below the price refused?		500failedServer error 500 instead of a refusal.
wrong_network
Is a payment on the wrong chain refused?		500failedServer error 500 instead of a refusal.
expired
Is an expired authorization refused?		500failedServer error 500 instead of a refusal.
replayed_nonce
Is a reused nonce refused?		500failedServer error 500 instead of a refusal.
not_yet_valid
Is a not-yet-valid authorization refused?		500failedServer error 500 instead of a refusal.
domain_version
Is a contract version supplied by the request ignored?		500failedServer error 500 instead of a refusal.
domain_chain_id
Is a chain id supplied by the request ignored?		500failedServer error 500 instead of a refusal.

Method and limits

An unpaid challenge is requested first. The remaining requests carry unreadable or altered payment headers with fabricated signatures. No valid payment is ever sent and no money moves. The responses demonstrate HTTP refusals, not isolated cryptographic field or replay security. At most 11 requests per origin including the challenge, one per second.

Original data (JSON)

Report history