APK verification
To ensure you’ve downloaded an authentic version of Network Survey, you can verify the APK signing certificate fingerprint before installing.
How to verify
Section titled “How to verify”To check the APK’s signing certificate:
Using apksigner (Android SDK):
apksigner verify --print-certs <apk-file>Official certificate fingerprints
Section titled “Official certificate fingerprints”Compare the SHA-256 fingerprint shown by your verification tool against the official values below. apksigner prints it in lowercase without colons (Signer #1 certificate SHA-256 digest: abf5ad29...), which is the same value.
Google Play Store
Section titled “Google Play Store”| Property | Value |
|---|---|
| Package | com.craxiom.networksurvey |
| SHA-256 | F5:85:5E:DE:9F:51:DD:EF:D7:2B:1C:D5:A2:29:76:1A:B7:35:2B:30:AD:4F:5F:CE:6D:E2:48:73:9F:4B:4C:79 |
GitHub releases, IzzyOnDroid, and direct APK downloads
Section titled “GitHub releases, IzzyOnDroid, and direct APK downloads”| Property | Value |
|---|---|
| Package | com.craxiom.networksurvey |
| SHA-256 | AB:F5:AD:29:11:FE:31:91:6F:4E:25:5C:17:33:A3:F6:BC:2C:AB:2F:28:16:C9:58:7D:E1:1A:41:58:71:AF:07 |
F-Droid
Section titled “F-Droid”Network Survey uses F-Droid’s reproducible builds feature. This means F-Droid verifies that their build from source matches the developer-signed APK, then distributes the original developer-signed version.
The signing certificate fingerprint for F-Droid APKs should match the GitHub Releases fingerprint listed above.
Related
Section titled “Related”- Build variants - Where to download each version
- Privacy policy - How your data is handled