This is a common issue in AWS too. User sets up a Route53 entry pointed at an S3 bucket, then later deletes the bucket but not the domain. Someone else then cre

This is a common issue in AWS too. User sets up a Route53 entry pointed at an S3 bucket, then later deletes the bucket but not the domain. Someone else then creates the same bucket again in their account (bucket names are globally reserved) and suddenly they can host content on a domain they don't own.