Free. No sign-up to run a check.

Know your deep links work before your users find out they don't

Paste your app's URL. We run the same checks an iPhone and an Android phone run when someone taps your link, then show you exactly what to fix.

Public files and store pages only. Nothing to install, nothing to configure.

Five checks. Every reason a link fails.

Most validators read your file. We read it the way Apple and Google do, then keep going.

Association files that pass on a real device

We fetch your apple-app-site-association and assetlinks.json without following redirects, because phones don't. Wrong content type, malformed app ID, lowercase fingerprint: we catch each one and name it.

Apple's cache versus your server

iOS never reads your file. It reads Apple's copy, which can lag your server by days. We compare the two and tell you when Apple is still serving the old version. It is the most common reason a fix appears not to work.

Both store listings, live

Everyone without your app lands on the store. We confirm the App Store ID resolves and the Play package still exists, so a pulled listing never turns into a dead link.

Your fallback page and certificate

Redirect chains, loops, insecure hops, error pages, and certificates about to expire. Each one quietly drops visitors. Each one shows up here with the exact hop that failed.

Path coverage and Android 15 rules

A valid file that does not cover the path you link to is still a broken link. We match your URL against your rules, check their order, and flag a missing catch-all.

Questions developers ask

Why does my universal link open Safari instead of the app?

Almost always one of five things: the file redirects or serves the wrong content type, the app ID is malformed, your components don't cover the path, Apple's cache is stale, or the tap happened inside an in-app browser. The checker finds the first four and tells you which one it is.

Why does Android report my domain as unverified?

Google fetches assetlinks.json over HTTPS with no redirects, and it needs the SHA-256 fingerprint of the key that signs your app on Google Play, in uppercase. An apex-to-www redirect or an upload-key fingerprint is enough to fail. The checker names the exact cause.

Does this install anything?

No. We request the same public files and pages a phone requests. No SDK, no script, no access to your app or your account.

Can it confirm the app opens on a device?

No server can. We verify everything that can be verified over the network and tell you plainly which steps still need a phone in hand.

What happens after I fix something?

Run it again. Every finding comes with the fix, and once you sign up we keep your report so you can compare runs. On paid plans we re-check daily and email you the moment something breaks, so you hear about it before your users do.