CertHunter

How many times have you needed an app’s SHA-1 or SHA-256 for a service integration, only to end up in a maze of CI secrets, cloud storage, old docs, and tribal knowledge?

That frustration is exactly why CertHunter exists.

When you work on multiple app flavors like dev, nightly, staging, and production, getting the right signing certificate can become surprisingly painful. Maybe the keystore lives somewhere in CI. Maybe it is stored in a cloud bucket nobody remembers. Maybe a release process signs the app at runtime, and nobody can confidently tell you which key was actually used.

And even if someone does hand you a keystore, one question still remains:

Is this really the certificate of the app that is installed on the device?

CertHunter answers that from the only source that truly matters: the installed app itself.

Instead of guessing from build pipelines and secret stores, CertHunter reads the signing certificate directly from apps already installed on your phone or test device. That means you can inspect the actual certificate that shipped, not the one people think shipped.

Built for developers, release engineers, QA, and mobile teams, CertHunter helps you:

- View SHA-1 and SHA-256 fingerprints of installed apps

- Inspect X.509 certificate details

- Check owner, issuer, serial number, and validity dates

- Verify which certificate a specific app flavor is really using

- Compare dev, nightly, staging, and production installs on the same device

- Copy certificate fields instantly for use in Google services and other integrations

This is especially useful when setting up or debugging integrations that depend on exact app signing certificates, such as:

- Google Pay

- Google Sign-In

- Maps and location APIs

- Firebase and Google Cloud integrations

- Any third-party service that requires SHA fingerprints or certificate verification

Why CertHunter?

Because the installed app is the source of truth.

If the app is already on the device, its signing certificate is already there too. No digging through CI. No asking around. No uncertainty about whether you are looking at the same key used in the actual build.

Everything is processed locally on your device. No data leaves your phone.

CertHunter is a small utility for a very specific pain point, but if you have ever lost time hunting for the “real” app certificate, you already know why it matters.