Universal Link & App Link Validator

Deep Link Hosting Requirements

HTTPS Protocol Required

Both Apple and Google require verification files to be served exclusively over valid HTTPS connections with trusted SSL certificates.

Exact File Locations

Apple expects AASA at `https://domain.com/.well-known/apple-app-site-association` (or root). Android expects Digital Asset Links at `https://domain.com/.well-known/assetlinks.json`.

Content-Type Headers

Servers must serve configuration files with the correct `application/json` content header, without HTML redirection headers.

What is Universal Link & App Link Validator?

Validate configuration formats for iOS Universal Links (`apple-app-site-association`) and Android App Links (`assetlinks.json`).

Universal Link & App Link Validator features

Available tool controls: Generate Configurations.
Input and option fields: iOS Team ID & Bundle ID:, Android Package Name & SHA256 Fingerprint:, Hosting Domain URL:.

Using Universal Link & App Link Validator in a development workflow

A validator can narrow down why a sample fails a syntax or rule check. Start with the complete input, inspect the first reported issue, and correct the source rather than only hiding the message. A pass means the checked rules were satisfied; it does not confirm business logic, compatibility, or security unless those checks are explicitly included.

Check the input before running the tool

Run a small example first and compare the output with an expected value before trying a larger case.
Pay attention to these page fields: iOS Team ID & Bundle ID:, Android Package Name & SHA256 Fingerprint:, Hosting Domain URL:. Confirm which fields are inputs, options, or output areas before processing.
The page exposes these relevant actions: Generate Configurations. Choose only the action that matches the result you need.
Confirm the result in the application or environment that will use it. The page only evaluates the information supplied here.

Keep the original available for comparison

Identifier and link rules vary by platform. Verify package or bundle identifiers and test links on the target OS and installed app version.

Frequently Asked Questions (FAQ)

This usually occurs if the AASA file fails validation, contains syntax errors, or if the user explicitly tapped the fallback badge in Safari's top right corner to bypass the app redirect.

You can manually verify domain handling via ADB command tools (`adb shell pm get-app-links package.name`) to check verification status on connected physical test devices.