Free AABReady Tool
Android Developer Verification & Package Registration Checker
Check your Android developer verification readiness and look up an Android package's registration status. Review package registration, SHA-256 signing certificate, developer identity, D-U-N-S, app signing, and 2026 distribution requirements.
Android developer verification protections begin on September 30, 2026 for participating app stores in Brazil, Indonesia, Singapore, and Thailand, with broader rollout planned for 2027.
Official package status
Check Google Android package registration
Enter your Android package name to check its current registration status using Google's Android Developer ID Status API. Add the production SHA-256 certificate fingerprint for a signing-certificate match check.
Leave this blank if you only want to check whether the package name is registered.
Readiness assessment
0/9 answered
Need help with Google Play package registration?
If your package is not registered, the status is unclear, or you are having signing-key or ownership-verification issues, review the package registration help page.
Get Package Registration HelpAnswer all questions to generate your readiness result.
Android Developer Verification 2026
What does this Android verification checker review?
This free checker reviews common Android developer verification readiness areas including developer identity, organization details, D-U-N-S information, package registration, Google Play App Signing, production signing identity, and whether you distribute through Google Play or other Android channels.
The package-status section can also check an Android package name using Google's Android Developer ID Status API. You can optionally provide the production SHA-256 certificate fingerprint to check whether the supplied signing certificate matches the registered package.
What verified developer information does Android require?
Depending on the account type and distribution path, Android developer verification may require verified identity information such as a developer's legal name, address, email address, and phone number. Organizations may also need a D-U-N-S number and a verified organization website.
Make sure the developer information you submit is accurate and consistent with the account, organization, and distribution details used for your Android apps.
September 30, 2026 Android verification deadline
Google says Android developer verification protections begin on September 30, 2026 for users installing apps from participating app stores in Brazil, Indonesia, Singapore, and Thailand on certified Android devices running Android 7 or later. The rollout is planned to expand globally in 2027.
Participating stores in the initial rollout include Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore, and GetApps.
Read Google's Android developer verification guidanceDo Google Play apps need package registration?
Yes. Google says most apps on Google Play have already been registered automatically using existing Play Console information. Developers should still check their Play Console Home page and complete registration for any remaining apps that require action.
For new Google Play apps, Play Console can automatically register the package name and connect it with the developer account. Apps that use an existing package name or an existing production signing identity may require additional ownership verification.
What does a certificate fingerprint mismatch mean?
If the package-status check reports a certificate mismatch, the package itself is registered, but the SHA-256 fingerprint you entered does not match the registered signing certificate. Confirm that you are using the production app-signing certificate rather than an upload key, debug key, or another certificate.
Google Play vs. outside-Google-Play distribution
Developers distributing through Google Play normally manage verification and package registration through Play Console. Developers distributing exclusively outside Google Play may need to use the Android Developer Console. If you distribute through both, review the registration path for every package and signing identity you use.
AABReady Support
Need help fixing a verification or package registration issue?
AABReady provides practical Android publishing support for Google Play Console, package registration, app signing, production access, closed testing, release readiness, verification, and related publishing problems.
Get Android Publishing HelpFAQ
Android Developer Verification Questions
What is Android developer verification?
Android developer verification connects a verified developer identity with the Android apps and package names that developer distributes. The requirements affect both Google Play and certain other Android distribution paths.
What verified developer information does Android require?
Depending on the account type and distribution path, Android developer verification may require verified identity information such as legal name, address, email address, and phone number. Organizations may also need a D-U-N-S number and a verified organization website.
What happens on September 30, 2026?
Android developer verification protections begin for users installing apps from participating app stores in Brazil, Indonesia, Singapore, and Thailand on certified Android devices running Android 7 or later. Google says the protections will expand globally in 2027.
Do Google Play apps need package registration?
Yes. Google says most Google Play apps have already been registered automatically, but developers should check Play Console and register any remaining apps that still require action.
What does a certificate fingerprint mismatch mean?
A certificate mismatch means the package name is registered, but the SHA-256 signing certificate fingerprint you supplied does not match the certificate associated with the registered package. Confirm the production signing certificate before relying on the result.
What if I distribute my Android app outside Google Play?
Developers who distribute exclusively outside Google Play may need to use the Android Developer Console for verification and package registration. The correct path depends on how and where the app is distributed.
Does this checker guarantee Android or Google Play approval?
No. The checker provides readiness guidance and a package-status lookup. Google and participating platforms control verification, registration, review, and enforcement decisions.
AABReady is an independent service and is not affiliated with or endorsed by Google. This checker provides general readiness guidance and does not guarantee verification, registration, Google Play approval, or continued app availability.