Android development
Paste the JSON, optionally enter the expected package and signing certificate SHA-256, then run a local check.
Paste assetlinks.json or load the example.
These steps have not been tested by this local checker.
JSON, package and certificate fingerprint are checked in this tab; no domain is contacted.
Paste assetlinks.json or load the example.
A link that opens in the browser may have a perfectly readable JSON file but no single statement authorizing the installed app. The Android App Links validator checks the statement shape and keeps package, relation and certificate fingerprint together.
Use this before publishing assetlinks.json or when comparing a Play App Signing certificate with a release build. An assetlinks.json validator can catch a missing relation or a SHA-256 fingerprint mismatch; live HTTPS delivery and device behavior still need separate checks.
See what the pasted file actually proves, then what remains to test.
The Android App Links validator accepts a match only when one android_app statement contains handle_all_urls, the expected package and the expected certificate fingerprint. Two half-matching statements do not become one authorization.
This Android App Links validator never fetches your domain. It reports local findings alongside a checklist for HTTPS, the well-known path, JSON content type, redirects, manifest autoVerify and device verification, leaving those items unconfirmed.
Paste the SHA-256 certificate fingerprint used for the installed app. With Play App Signing, use the App signing key certificate from Play Console; a local upload or debug key can differ. The field also accepts a 64-character hex string without colons.
Checking is manual. Any change to JSON, package or fingerprint immediately marks the previous report stale and disables export. Ctrl/Cmd+Enter reruns it; malformed JSON points to a line and column.
A valid DAL array, a matching statement and a deployed App Link are different claims. The report lists all declarations and issues, including unresolved include files. Copy and download contain the complete report even when the visible list is paged.
The Digital Asset Links checker parses the top-level array, relation lists, android_app and web targets, and points to an indexed field when a value is malformed. An include pointer is recorded without being fetched.
Expected SHA-256 input tolerates letter case and optional colons for pasting. File entries are also checked against the canonical uppercase colon form; SHA-1 and file hashes cannot stand in for a signing certificate.
The report counts handle_all_urls declarations and tests package and fingerprint inside the same one. Other DAL relations remain visible but do not authorize Android App Links.
Copy or download the full structured report after a current check. Long declaration and issue lists show 50 items at a time in the panel, while the export keeps every item.
A syntactically correct file can still lack the matching handle_all_urls statement, use the wrong Play App Signing certificate, or be served with a redirect. The Android App Links validator narrows the local declaration problem; then inspect the live URL, manifest and device state.
Host it at https://your-domain/.well-known/assetlinks.json on every hostname your app claims. Serve JSON directly without redirects and check its content type. This page gives the checklist but makes no HTTP request.
Add the SHA-256 fingerprints for certificates that sign builds which need to verify the domain. Debug and release builds often use different keys; a Play-distributed release usually needs the Play App Signing certificate, not merely the upload key.
Yes. Put separate android_app statements in the array, each with its own package and certificate fingerprints. This checker evaluates each statement independently, so a package from one app cannot borrow another app’s fingerprint.
First run the local check here, then inspect the public HTTPS file and use adb shell pm get-app-links with the installed package. The Digital Asset Links checker cannot see server response headers, the installed signing key or device verification status.
A declaration still looks wrong?
Paste your pre-release statement list into the Android App Links validator, compare the app signing certificate, then take the deployment checklist to your server and device.
JSON and comparison values stay in this browser tab.