SFN

Agreed. I set up a forwarding address to my new domain (hosted by another DNS registrant fortunately) and it's been 4 days and I'm still having forwarding issues. SSL certificate shows as invalid with a ERR_CERT_COMMON_NAME_INVALID error for some browsers. On top of that squarespace's UI is not allowing me to turn on path forwarding, even if I update the setting to "true", the network request would send with that value as "false" (obviously a bug). I've reached out to support and they have not responded after 3 days due to "high volume"... Of course there's a high volume! You're in way over your heads and you're providing a shoddy service with too many issues for your poor support team to keep up with--corporate greed at its worst... This has been an extremely frustrating experience. I'm baffled that a company of this caliber would branch off into something that is completely out of their realm and execute it in such a poor way. This issue is affecting my company's SEOa nd I'm getting alerts from Google's web crawler about indexing issues. Just a quick Google search shows that squarespace has had a reputation for being notably bad at everything they do besides their website builder service. Whoever is in charge of these decisions at squarespace is not doing a very good job. I was fine on Google Domains, why did you guys have to come and mess everything up??