Are auto-checked links cached in Android M?

I am currently working on running some tests to see how the tried and tested link system works with Android M and ended up in an interesting outcome. The usual flow is this:

• Install app
• GET to $ {HOST} /. The well-known /statements.json got fired.
• If approved (server completed, key is valid, etc.), all verified links will be deeply linked to the application

When the server is off, we see this

• Install app
• GET to $ {HOST} /. The well-known /statements.json got fired.
• Unapproved, links show popup
• Uninstall and reinstall the app
• GET to $ {HOST} /. The well-known /statements.json got fired.

However, if the server exits after the initial check, we see something interesting

• Install app
• GET to $ {HOST} /. The well-known /statements.json got fired.
• Verified deep links
• Disable server
• Remove the app and reinstall the app
• Net call failed

If we wait a certain amount of time before reinstalling, then a network call will be made and everything will work fine. It seems that data and / or application cached data -> is cached somewhere that was not destroyed when the application was uninstalled.

• Is this behavior expected?
• Why does this happen and always hit the server?
• Where will this be cached if not with the application?