My anomaly
Available after successful Run checker.
Runs anomaly analysis for the collected fingerprint.
Session is not initialized. Start from Checker with Run checker.
Anti-Fraud Layer
Product-level architecture, use case mapping, and future-ready integration placeholders.
Checker Actions
Trial Program
Validate Fraudnode against representative production traffic
Use a longer evaluation window to measure classification behavior, tune T0 and T1 policy thresholds, and prepare the persistence and isolation model for a production contour.
Designed for teams ready to test policy behavior, traffic distribution, escalation rates and operational fit before production deployment.
Compact decision payload
criticalClassification
dirty
proxy
90%
Class risk score
Operating system
Linux
Browser
Chrome
Device
Stationary
Final probability94.75%
Access window
30 days
Access expires when either the time or request limit is reached.
Request quota
10,000
Orca tracks usage, key status, remaining quota and expiry.
Runtime contour
Spider + Penguin + DB
Shared tenant-isolated access with full persistence for evaluation.
Decision Flow
Start fast, escalate only when policy requires it
T0 is the default request. T1 is not automatic: your application decides whether the score or business context justifies a longer second-stage collection.
01T0 · Fast path
Collect the current fingerprint
Spider captures TCP, TLS, HTTP and JavaScript signals. Orca adds GEO enrichment and prepares the canonical Penguin payload.
TCPTLSHTTPJSGEO
02Client policy
Evaluate the compact decision
Your policy examines class score, probability and risk class. Clean and clearly dirty traffic can be handled immediately.
scoreprobabilitythresholdrisk class
03T1 · Optional
Escalate gray-zone traffic
When more evidence is required, run a longer collection. T1 rebuilds T0 and adds enabled DNS, blacklist and UDP/QUIC context.
T0 rebuiltDNSblacklistUDP / QUIC
04Your decision
Apply the business action
Orca and Penguin return structured evidence. The final allow, challenge, recheck or block decision remains inside your product policy.
allowchallengerecheckblock
What You Receive
Structured evidence, not a black-box label
- Compact classification, probability, class risk and recommended action.
- Detected OS, browser and device type for policy and investigation workflows.
- Per-signal parameters, inconsistencies and class-specific contributing reasons.
- Optional T1 context linked to the original T0 request.
Trial Fit
Validate policy behavior on representative traffic
Measure class distribution, tune escalation thresholds and decide which production persistence profile fits your security and throughput requirements.
Important
Orca and Penguin provide classification and evidence. Your application remains responsible for the final business decision and user treatment.
Contact
Plan your trial contour and success criteria
Tell us about the protected flow, expected traffic and the decisions you want to automate.