Android developer verification checker

Know if your app is registration-ready.

Check an Android package and its signing certificate against the official status service. Get a clear answer before the September enforcement window 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, then verifies the package 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.

The API response is only useful when a release team knows what to do next. Each state maps to a focused explanation and a safe remediation sequence.

REGISTERED

The package or package-and-certificate pair is recognized. Continue with store and policy checks.

Interpret result →

NOT_REGISTERED

Recheck the production identity, then complete registration in the appropriate official console.

Start remediation →

ANOTHER_CERTIFICATE

The package exists, but the queried fingerprint differs. Investigate signing history before changing keys.

Trace signing identity →
Initial milestone
093026

Regional enforcement begins for participating stores on certified Android devices.

Scope the deadline correctly

Four countries.
Seven stores.

Brazil, Indonesia, Singapore and Thailand form the first phase. Global expansion begins in 2027, so teams outside the initial footprint still need an inventory and signing plan.

Brazil →Indonesia →Singapore →Thailand →

The readiness
field manual.

Focused pages for package identity, signing, regional rollout and release automation. Every page exists to answer a distinct operational question.

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 → Small-audience path

Android limited distribution account requirements

Evaluate Android's limited distribution account for teaching, hobby projects and very small device groups without government ID verification.

Read field note → User-controlled path

Android advanced flow for unverified apps

Understand the advanced installation flow for experienced users and why it is not a substitute for developer registration.

Read field note → Release deadline

Android verification deadline: September 30, 2026

Map the September 30, 2026 Android developer verification milestone to affected countries, stores and release actions.

Read field note →