Reference
Every check, explained.Mechanism · threat · bypass · references.
One page per signal the native modules emit. Each explains what the code actually inspects, the exploit it is meant to surface, how a motivated attacker who controls the device evades it, and where to read more — OWASP MASTG, Apple and Android platform docs, and the tooling ecosystems. Each check also shows whether it has been seen firing in a validated test run.
- Checks
- 23
- iOS
- 10
- Android
- 13
- Block by default
- 21
- Seen firing
- 12
Jailbreak
Jailbreak4 checks
Root
Root6 checks
Hooking & instrumentation
Hooking & instrumentation4 checks
Debugger
Debugger2 checks
App tamper
App tamper4 checks
Emulator / simulator
Emulator / simulator2 checks
Read first
Every check here is a client-side risk indicator, not attestation. Each can be bypassed by an attacker who fully controls the device. Use them to raise the cost of attack and to gate low-to-medium value flows; for high-value actions pair them with server-side Apple App Attest / DeviceCheck and the Google Play Integrity API.