/
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
      Overriding verdict reasons
      Intelligent Rate Limiting
    Enforcement
      Enforcement overview

    • Protected Auth

        • Overview
        Handling challenges
    Integration steps
      Configure custom domains
      Test your integration
      Privacy and compliance considerations
    Reference
      Warning Flags (Verdict Reasons)
Get support on SlackVisit our developer forum

Contact us

Fraud and Risk Prevention

/

Guides

/

About Stytch Fraud and Risk

/

Integration steps

/

Configure custom domains

Configure custom domains

Stytch Device Fingerprinting supports custom domains in order to reduce interference from ad-blocker plugins and privacy browsers, which may block requests to third-party sites.

Ad-blockers are used by a significant proportion of real users, but malicious attackers will also try to block fingerprinting to avoid detection. When Stytch Device Fingerprinting detects an ad-blocker, the resulting fingerprints receive a BLOCK verdict action, with a verdict reason of AD_BLOCKER_DETECTED.

You can set up two custom domains (CNAMEs) to help distinguish between...

Restricted content: Access to this full documentation page is limited to Stytch Device Fingerprinting customers. To view it, log into your existing customer account or request access to the product.

Please log in to access this page.

For security, this page is restricted to workspaces using Stytch Device Fingerprinting.

Log in to Stytch

Interested in device fingerprinting?

Add fraud protection to your auth stack with advanced device fingerprinting that goes beyond CAPTCHA and WAF.

Get started