That isn't the issue. If your key got deactivated for moving from place to place too quickly (this won't happen, it only happens when it's moving thousands of miles in extremely short periods), then you would get a message saying 'Inactive Key'.
Actually, it would first say "Full version unlocked!" because the local key checking function decides it is a valid combination, then it sends it to the auth server, which sends back that it is disabled by using one of many possible error messages, such as "ID does not exist", and when that reply arrives at your blockland it will change the message to the error.