Heh. You’re absolutely right, I misspelt the domain. Point being, sometimes you have different domains that belong to the same entity and you need to bridge them; this seems strange to small companies, but happens quite often in enterprise.
Blizzard's Battle.net does, or at least did at one point.
In 2020 my friend couldn't add a new credit card to his account because browsers updated their same-site cookie behavior.
They were setting their JSESSIONID cookie wrong when doing oauth behind-the-scenes which caused a nice 302 redirect loop.
For whatever reason the API calls required both *.battle.net and account.blizzard.com.
Edit: fixed the domain to actually make the point I was trying to make.