If DNS is wrong, that server can get a domain validated certificate. What I am imagining here is that you set a cookie with Domain set, and not __Host, possibl

If DNS is wrong, that server can get a domain validated certificate. What I am imagining here is that you set a cookie with Domain set, and not __Host, possibly because you need the cookie to be accessible on multiple domains, and then someone sets up a CNAME that points to a third party hosting service without thinking about the fact that that would leak the cookie. Sure