They support two-factor auth (almost no one else does), and have nicely scoped cookies (HTTP only, Secure flag, etc.).
Now, if one of your authenticated users visits the wrong subdomain, they are directed to a server of name.com's choice.
That server now has access to your user's session ID (using Javascript or PHP or whatever to read the cookie).
Thanks for the correction.
They support two-factor auth (almost no one else does), and have nicely scoped cookies (HTTP only, Secure flag, etc.).