/
Contact usSee pricingStart building

    About Stytch Fraud and Risk

    Introduction
    Use cases
    Device Fingerprinting
      Overview
      Fingerprints
    • Verdicts

      • Verdicts overview
        Allow
        Block
        Challenge
        Not Found
    Getting started
      Device Fingerprinting API
      DFP Protected Auth
    Decisioning
      Decisioning overview
      Setting rules with DFP
      Intelligent Rate Limiting
    Enforcement
      Enforcement overview
    • Protected Auth

      • Overview
        Handling challenges
    • Strong CAPTCHA

      • Overview
        Getting started
Get support on SlackVisit our developer forum

Contact us

Fraud and Risk Prevention

/

Guides

/

About Stytch Fraud and Risk

/

Device Fingerprinting

/

Verdicts

/

Not Found

Not Found errors

If the telemetry_id is missing from the lookup request, or we cannot find it in our records, we will return a 404 telemetry_id_not_found error.

Not Found results in DFP API

When you receive a 404 in the Fingerprint lookup response, we recommend blocking the request from proceeding. A missing or invalid telemetry ID could be a sign of an attacker trying to bypass DFP protections by generating fake telemetry IDs or not passing them into requests.

Not Found results in DFP Protected Auth

When DFP Protected Auth is enabled in Enforcement mode and the telemetry_id is missing or not found, our SDK will always prevent the user's request from proceeding.

Not Found results in DFP API

Not Found results in DFP Protected Auth