/ 01TOOLFREE TOOLS · FOR DEVELOPERS

App Links checker

Check the two files that let a domain open your app: assetlinks.json for Android App Links and apple-app-site-association for iOS Universal Links. No account needed.

The domain your links use. A full URL works too; we keep only the host.

What these files do

When someone taps a link to your domain, the phone opens your app only if the domain says it may. Android reads https://your-domain/.well-known/assetlinks.json: your package name and the SHA-256 fingerprint of the certificate that signs the app. iOS reads https://your-domain/.well-known/apple-app-site-association: your Team ID, bundle ID and the paths the app handles. If a file is missing, redirected or malformed, the link opens the browser instead.

What this checks, and what it can't

It fetches the files the way a verifier would (https, no redirects allowed, JSON content type) and checks their format: statements, package names, fingerprint format, app IDs, paths and components. It checks the files on the domain, not how a particular phone behaves: Android also compares the fingerprint with the app installed on the phone, and iPhones read the file through Apple's CDN, which caches it. To fix a phone that still opens the browser, see Troubleshooting.

If your links run on a Strait link domain (<handle>.strait.link), Strait serves both files for you from your app settings; see App Links & Universal Links.

Running both checks together is useful when one domain serves Android and iPhone links, which is most domains: a CDN rule, a redirect from the bare domain to www, or a firewall that blocks unknown user agents usually breaks both files at once, and fixing one without the other leaves half your audience in the browser.

Want one platform, with every rule explained and a fix snippet? Use the assetlinks.json checker for Android or the AASA validator for iOS. To write the files, use the assetlinks.json generator and the AASA generator.

We fetch only these public files, with the user agent StraitAppLinksChecker/1.0. Reports are kept in memory for one minute, so repeat checks don't hit the server again, and are not stored.