ECHOSCAN
UNQ
STB
#···
About Blog

About EchoScan

EchoScan is a device identity and access-risk service. It connects browser-environment collection, device continuity, and server-side risk reports so developers and security teams can understand the technical context and risk state behind a visit inside their existing backend.

Built from long-term browser research

The project grew from sustained research into Chromium, anti-fingerprinting browsers, and differences among runtime environments. Small variations in browser versions, rendering paths, hardware capabilities, fonts, timezones, networks, and automation tools shape what a website can observe during a visit.

Those conditions keep changing, so the research continues. EchoScan follows the same discipline: verify environmental facts first, then expose stable results through a business-facing product contract.

From research tool to service

The public Scan lets any visitor inspect the current browser environment without an account. Browser Verifier serves developers inside customer sites and returns only a server-issued Imprint after a successful run.

The customer backend uses a Secret API Key to query Report API v1. Lite and Pro share one Endpoint, and the plan determines response depth. Customers read risk.status and combine it with account, transaction, entitlement, and verification data before choosing a final action.

Who the service supports

EchoScan serves developers, security teams, and risk teams that need device continuity and access-risk context. It is especially relevant to SaaS products, AI tools, API platforms, free trials, and other online services that grant costly resources.

The research also covers browser variation, anti-fingerprinting environments, automation, network risk, and privacy boundaries. The goal is clear technical evidence that customers can interpret inside their own business context.

Independent research background

EchoScan continues the working style of an independent creator engaged in long-term research and steady iteration. Product design, detection research, developer experience, and public documentation all emphasize verifiable facts and explicit boundaries.

The project evolves as browsers, operating systems, networks, and abuse techniques change. Public contracts stay stable while internal implementation continues to improve.

The boundary between public capability and internal rules

The public Report includes device, browser, operating-system, network, risk status, and the continuity information allowed by the plan. Pro also includes product-level risk reasons and access to History.

Detector names, raw evidence, thresholds, weights, debug data, and bypass conditions stay outside the public interface. This boundary protects detection effectiveness and gives customers a stable set of business-facing fields.

Contact

For general questions, email contact@echoscan.org. For integration and technical support, use support@echoscan.org. Privacy and security questions can be sent to security@echoscan.org.

Read the EchoScan platform overview to see the complete product flow.