Android developer verification checker

Know if your app is registration-ready.

Check an Android package and signing certificate against the official status service. Get a clear next step before enforcement reaches your release.

30 Sep 2026First enforcement
4 countriesInitial footprint
3 statesActionable output
Package registration probeOfficial API
Required
Optional · safer match

Turnstile loads when you interact with the checker and protects the official status request.

No APK. No private key. Query results are not written to a database.

Official response
WAITING

Open guide →
01package identity02certificate match03regional exposure04release action

Three answers. Zero ambiguity.

A status only helps when a release team knows what to do next. Every result points to a safe, focused follow-up.

REGISTERED

The package or package-and-certificate pair matches the official record.

Interpret result →

NOT_REGISTERED

The package has no completed registration record and needs investigation.

Interpret result →

CERTIFICATE MISMATCH

The package exists, but the submitted certificate does not match the registered identity.

Interpret result →

Field notes for release owners.

Focused guidance for package identity, signing, rollout and automation.

Start here

Android developer verification requirements

Understand Android developer verification, app registration, signing certificates, regional enforcement and what to prepare before September 30, 2026.

Read field note →Core workflow

How to check Android app registration status

Check whether an Android package is registered and whether its production signing certificate matches Google's registration record.

Read field note →Identity input

Find an Android package name without guessing

Locate the exact Android application ID or package name in Gradle, an installed app, Play Console or an APK before checking registration.

Read field note →Signing identity

APK signing certificate SHA-256 fingerprint

Extract and normalize the SHA-256 fingerprint used to sign an Android release without exposing a private key.

Read field note →Certificate map

Play App Signing developer verification guide

Understand which certificate fingerprint matters when Google Play manages the app signing key and your CI uses a separate upload key.

Read field note →Alternative distribution

Android developer verification for sideloaded apps

Prepare package names and signing certificates for apps distributed through websites, open-source channels or third-party stores.

Read field note →
Open the full guide →
First enforcement

The first rollout is regional. Your release process should be global.

Enforcement starts in Brazil, Indonesia, Singapore and Thailand across participating stores, then expands. Prepare every active package now.

Prepare for the deadline →
Brazil →Indonesia →Singapore →Thailand →