Another one bites the dust at Codesmith

So they cannot control the domain or direct it anywhere else because that is configured under DNS which is under AWS. The domain registrar can point the domain to a new DNS configuration to work around that but the domain registrar in this case is also AWS. What they should have done on day one reboot become irreplacable, then get a semi peromanent redirector domain like [cs.site](http://cs.site) or something, and then change all of their socials to the new redirector and have that redirect to become irreplacable. Then whenever they get their site back they coulld have it redirect back to [codesmith.io](http://codesmith.io) This doesn't solve the email problem and the user data problem though. They could re-host CSX but people would have to create new accounts and it might be a mess, but it would be better than notihng. Email is a huge problem - because a lot of other service will send 2-fac emails to emails, so even if they can login temporarily, it's possible with a long outage that they lose access to critical government reporting, payroll, and other critical systems. So if it was me I probably would have bought [codesmith.org](http://codesmith.org) for $10K, setup the new site as a new permanent home, setup new emails with this as an alias in Google, then change all logins to using .org, etc... This situation sucks for them even if it's entirely their fault that doesn't mean it doesn't suck, but the way they handled it is why they are losing staff and facing problems.