DChecker — see what changed inside Android
Diagnose the integrity of an Android environment: bootloader, root, hooks, SELinux, virtualization, attestation and location — with evidence correlated across layers instead of a single superficial verdict.
- Android 10+
- No root required
- No telemetry
- RU / ZH / EN
Latest APK: DChecker-2026.11.19-096bfcbc4e11.apk
One environment. Several independent lenses.
Review Native Root and Network Risk next.
- 0Danger
- 4Warning
- 345Ready
- 235Not run
Evidence you can trace, not a blanket verdict
Every finding follows an observable chain: the signal, the subsystem that answers, the implementation and the applicable Android, kernel or vendor context. Results are diagnostic evidence with confidence levels — not a claim that a device is safe or compromised.
Read the same fact through different layers
Framework APIs, native JNI probes, shell, procfs, sysfs and kernel observations are compared. A disagreement between lenses is itself a useful signal.
Connect findings across detectors
Nineteen rules link related evidence, such as KernelSU confirmed by two independent layers or spoofed location combined with a virtual environment.
See each failed check and export the result
The dashboard names individual problems and their severity. Scan history, exit logs and a complete text report support analysis outside the phone.
24 detector groups and more than 500 checks
The 24 detector groups organise more than 500 individual checks across the boot chain, operating system, root and injection surfaces, trusted execution, applications, device identity, location and network behavior.
Boot and OS
- Bootloader, AVB, vbmeta and dm-verity
- Custom ROM and system properties
- Kernel and SELinux checks
Root and injection
- SU paths, processes and root managers
- Native root, mounts and namespaces
- Zygisk, LSPosed and Xposed
Trusted environment
- TEE, Keystore and KeyMint
- Attestation and RKP checks
- Play Integrity Fix inconsistencies
Runtime environment
- Virtualization and ADB runtime
- Memory injection and heap residue
- Automation surfaces
Apps and identity
- Dangerous and hidden applications
- Data, identifiers and sandbox audit
- Hardware profile and device information
Location and network
- GPS, SIM, cell, Wi-Fi, GNSS and IP evidence
- Mock-location and location risk
- VPN tunnels, NAT traces and proxies
Install and scan locally
- Download the APK. Use the latest DChecker package from the software page or the button above.
- Install on Android 10 or newer. Root is not required, although modified environments expose more diagnostic evidence.
- Open DChecker. Scanning starts automatically and cards fill as detectors complete.
- Export the report. Share or analyse the complete result, including detector sections and correlations.
Privacy and limitations
Scanning runs locally and does not send device data to Device Changer. Android sandbox restrictions can make some surfaces unreadable without root or permissions; that refusal is reported as a separate state rather than a clean result.
Absence of evidence is not proof that no modification exists. DChecker distinguishes detected, not observed, not observable from this process and not applicable. It does not predict whether another service will accept a device.
Origin and license
DChecker is developed from Duck-Detector-Refactoring and its contributors, with its own branding, localization and expanded checks. Code is distributed under the Apache License 2.0.