It seems like spinning up a Phantom instance and getting the necessary information can take ~10 seconds, which is a long time for a user to sit around looking at a spinner or the like.
Perhaps a quick purge request to the for the URL provided by the user and abort the Phantom process in the case of a 403 response would work.
Maybe delay starting Phantom until that check goes through.