Does INCLUDE prove Universal Links work on a device?

No. It is a local result for the supplied document and URL. Hosting, app entitlements, device caches, OS behavior, and the real signed application still need verification.

Are the demonstration application IDs deployable?

No. Replace the public placeholder Team ID, bundle ID, package name, and certificate fingerprints with the authorized values for your own application.

Does the tool retrieve the domain association files?

No. It builds or simulates supplied text. Check the actual well-known HTTPS endpoints and platform behavior as part of a separate deployment test.

Mobile

App Link Association Studio

Build and simulate Apple AASA and Android assetlinks routing rules.

Online tools Pricing

Input0 characters

Result0 characters

Prefer a native workflow?

Keep App Link Association Studio one shortcut away.

DevSexy for Mac puts the same private workflow in a focused desktop app, with global shortcuts and no browser tab to manage.

Global shortcutOffline-readyLocal processing

Try the Mac app free

This browser tool remains free.

Association studio · identity before routing

A valid file is only one side of the trust handshake.

The website, signed app, system verifier, and URL policy must agree. This studio builds the local evidence and simulates ordered Apple rules without pretending it can certify your production host or device cache.

Two-sided trust handshake

iOS APP

TEAM ID + BUNDLE ID

associated-domains entitlement

WEBSITE

HTTPS ORIGIN

AASA or assetlinks at exact path

ANDROID APP

PACKAGE + SHA-256

manifest intent filter + installed signer

Identity rails

Apple app IDABCDE12345.com.example.app

Team ID prefixes bundle ID

Android targetcom.example.app

application ID

Release signerAA:BB:…:32 BYTES

installed certificate fingerprint

Play App SigningPLAY CERTIFICATE

often differs from local upload key

Ordered route court

ORDERCOMPONENTRULINGEVIDENCE

01/private/*EXCLUDEfirst match stops

02/products/*INCLUDEpath evidence

03/search/* + queryINCLUDEpath and query

04/help/* + fragmentEXCLUDEfragment evidence

05*INCLUDEfallback

Platform divergence map

CONTRACTAPPLEANDROID

Website identityAASA appIDsDigital Asset Links target

URL scopecomponents path/query/fragmentmanifest intent filters

Website dynamic rulesAASA componentsAndroid 15+ dynamic components

Signing evidenceTeam ID + bundle IDSHA-256 certificate

Local simulationordered first-match policyidentity statement only without manifest

Production hosting runway

01 · Apple/.well-known/apple-app-site-associationHTTPS · no extension · JSON MIME · no redirect

02 · Android/.well-known/assetlinks.jsonHTTPS · application/json · no redirect

03 · Every hostseparate origin evidencesubdomain and apex verify independently

04 · CachesApple CDN / device verifierdeployment is not immediate local state

05 · Legacy Apple boundary128 KB uncompressedkeep rules concise

Failure ladder

FETCH

file unreachable or redirected

PARSE

wrong MIME or malformed JSON

IDENTITY

app ID/package/signer mismatch

APP CONFIG

entitlement or manifest missing

ROUTE

ordered rule does not match

DEVICE

install/cache/browser behavior

Security perimeter

Routed parameters remain untrusted input.

Association proves control relationships, not authorization. Validate and normalize the URL, require authentication, check resource ownership, confirm destructive actions, and preserve a safe web fallback.

Run a reproducible example

Simulate ordered AASA include/exclude rules locally using a public application ID.

Using an example replaces the current input, reference input, operation, and options. Public demonstration data only.

Match a product route

The AASA document excludes /private/* before including /products/*. The candidate is /products/17.

Input

{"applinks":{"details":[{"appIDs":["ABCDE12345.com.example.demo"],"components":[{"/":"/private/*","exclude":true},{"/":"/products/*"}]}]}}

The local simulator returns INCLUDE under the supplied rules. It does not fetch the domain or prove OS association.

INCLUDE

Exercise an exclusion rule

Use the same document with /private/17 as the candidate URL.

Input

{"applinks":{"details":[{"appIDs":["ABCDE12345.com.example.demo"],"components":[{"/":"/private/*","exclude":true},{"/":"/products/*"}]}]}}

The earlier exclusion returns EXCLUDE. Rule ordering must be reviewed before deployment.

EXCLUDE

Continue with a related task

URL Inspector & Query Editor

Separate, edit, encode, and rebuild every URL component.

JSON Formatter & Validator

Format, validate, minify, inspect, and query JSON with precise syntax diagnostics.

X.509 Certificate & PEM Inspector

Decode certificates, SANs, key usage, and validity without sending private material away.

Repeat the task in DevSexy for Mac

Use the native app for repeated offline work and direct Option shortcuts.

Direct answer

What is App Link Association Studio?

Generate AASA and assetlinks.json files online, inspect Apple and Android app identity, and simulate ordered Universal Link routing before deployment.

What can it do?

Apple AASA
Android assetlinks
Simulate

How to use App Link Association Studio

01
Prepare the input
Provide your association document and exact candidate URL.
02
Choose the operation
Simulate AASA rules or generate a platform-specific association document.
03
Review the evidence
Validate HTTPS hosting, content type, platform identifiers, signing fingerprints, and actual device behavior separately.

Frequently asked questions

Does INCLUDE prove Universal Links work on a device?: No. It is a local result for the supplied document and URL. Hosting, app entitlements, device caches, OS behavior, and the real signed application still need verification.
Are the demonstration application IDs deployable?: No. Replace the public placeholder Team ID, bundle ID, package name, and certificate fingerprints with the authorized values for your own application.
Does the tool retrieve the domain association files?: No. It builds or simulates supplied text. Check the actual well-known HTTPS endpoints and platform behavior as part of a separate deployment test.