LinkLint

When a web link does not open an app as expected, the problem may be in the website association file, app identity, URL rules, or network response. LinkLint brings those checks into one clear report. Enter a domain or issuer to see what passed, what needs attention, and the evidence behind every result. Built for release checks and troubleshooting • Check whether AASA is reachable and whether its app declarations and Universal Links rules are valid • Review app identifiers, certificate fingerprints, and website-declared URL matching rules in assetlinks.json • Test URL paths, queries, fragments, and exclusions with a step-by-step matching trace • Inspect issuers, endpoints, capabilities, and security settings in OIDC Discovery and OAuth authorization server metadata Turn each result into a useful next step Every issue explains what happened, why it matters, likely causes, and what to change. PASS, WARNING, FAIL, NOT CONFIGURED, and UNKNOWN make it easy to separate a valid setup from an optimization, an error, a missing configuration, or insufficient evidence. Reports preserve HTTP status, headers, manual redirects, DNS resolution, the actual connection address, TLS details, certificate summaries, the complete response body, and SHA-256. When you need to go deeper, the original evidence is already there. Local files and scan history Import AASA, assetlinks.json, OIDC, or OAuth metadata from Files and validate it on your device. The free version keeps the five most recent scans for quick review. Free inspections, optional Pro upgrade The free version includes all four protocol inspections, diagnostics, network evidence, local file validation, and URL rule testing. One LinkLint Pro purchase adds regional App Store availability checks, platform association insights, semantic comparisons between scans of the same target, and unlimited local history. Local by design No account is required. Scan reports and history stay on your device and are not automatically uploaded or synced. App Store information helps identify declared apps but never changes the protocol result. Important: A passing website-side check does not guarantee that a link will open an app on a real device. Final behavior also depends on app entitlements or manifests, signing, installation state, system caches, user settings, and in-app routing.