The AASA Validator, formerly the Universal Links Validator, can be used to test if your website is properly configured for Universal Links. We’ll test your domain against Apple’s requirements for hosting your Apple App Site Association file along with
what we have seen in production that leads to a successful implementation of Universal Links. Properly setting it up is a critical step in ensuring that your Universal Links work properly so you’re able to give your iOS users the best
possible experience. If your AASA validates, and Universal Links are still broken, you can use the
Universal Links Validator to test your Xcode project configuration.
In addition to your domain, you may also enter your Apple App Prefix and Bundle Identifier to validate that the correct values from your project are present. If your Apple App Site Association file is properly formatted,
we’ll return it for you. If not, we’ll show you which tests failed or did not run due to a previous failed test.
Below you’ll find a list of tests that were run and a copy of your apple-app-site-association file:
- {{ displayMessage('badDns', didErrorOccur='success_without_congrats') }}
- {{ displayMessage('httpsFailure', didErrorOccur=false) }}
- {{ displayMessage('serverError', didErrorOccur=false) }}
- {{ displayMessage('badContentType', didErrorOccur=false) }}
- {{ displayMessage('invalidJson', didErrorOccur=false) }}
{{ prettyPrintAASA(results.aasa) }}
{{ prettyPrintAASA(results.aasa) }}
{{ prettyPrintAASA(results.aasa) }}
- {{ domain }} – This domain has some validation issues
- A request to this domain failed.
- {{ displayMessage('badDns', results.errors.badDns) }}
- {{ displayMessage('httpsFailure', results.errors.httpsFailure) }} Learn More
- {{ displayMessage('serverError', results.errors.serverError) }} Learn More
- {{ displayMessage('badContentType', results.errors.badContentType) }}
- {{ displayMessage('invalidJson', results.errors.invalidJson) }} Learn More