Beaconing detection
Command-and-control clients and most stalkerware "phone home" on a timer, not on demand: check in every few minutes, upload, wait, repeat. ENCLAY watches the interval between an app's connections to the same destination and flags the pattern when it's suspiciously regular, the way a person's real usage rarely is.
app.example → 10.2.4.19 · 41 connections · every ~4.0 min (σ 0.15) · flagged: regular-interval beaconing
Redirect-chain detection
Clusters a browser's rapid burst of connections to different hosts into one navigation chain, and flags it if any hop led to known-malicious infrastructure. Scoped to actual browser apps, not background app traffic.
Permission-to-network correlation
Flags a new destination that appears within minutes of a sensitive permission grant (camera, microphone, or location), a common signature of data being collected and immediately shipped out.
Live Feed
Every connection, every app, in real time, searchable by host, IP, organization, country, or threat category.
App Profile
Per-app host history, data usage, and connection patterns, isolated from the rest of the device's traffic.
Domain age (RDAP)
Flags infrastructure registered days, not years, ago, one of the more reliable phishing and malware tells.
Reverse DNS & hosting class
Tells you when a destination sits on bare cloud/VPS infrastructure instead of a named, recognizable service.
Certificate inspection
Subject, issuer, expiry, and self-signed detection, read directly from the live TLS handshake.
DNS enrichment
Opt-in: resolves a blocked domain's real IP purely for display, so a DNS-level block still shows a real IP and ASN instead of the meaningless in-tunnel address.
Immediate new-install audit
A newly installed app gets its permission snapshot the moment it lands, not after waiting up to an hour for the periodic scan — no blind spot in that app's permission timeline from minute one.
Install-age-aware permission correlation
Enriches the new-destination-after-permission-grant signal with how long the app had sat quietly installed before asking: a permission granted the day an app was installed reads very differently from the same grant six months in.
Possible interception detection
A domain that has consistently used TLS 1.3, invisible to any inspector, suddenly showing a visible certificate has almost no innocent explanation: most proxy-based interception tools (a pushed workplace or parental-control certificate) can't see or rewrite an encrypted TLS 1.3 handshake, so they force a downgrade to see it. Flagged only once independently observed from more than one app, the same corroboration discipline used everywhere else here. It cannot see interception by a competing on-device VPN app — Android only runs one VPN at a time — and says so plainly rather than overclaiming.
Unusual upload-volume detection
Compares an app's upload volume today against its own recent daily average, catching a bulk data dump that happens at an ordinary time of day and would otherwise slip past timing-based detection entirely.
Unexpected-network resolution
Notices when an app's own connection to a familiar domain resolves onto a network it hasn't itself seen for that domain recently. Deliberately scored as a weak, corroborating signal only: switching Wi-Fi networks and ordinary CDN failover produce the same pattern completely legitimately.