Squarespace as Domain Registrar: Navigating a Renewal Impasse and What Comes Next
Summary of the situation
A small business is facing a renewal deadlock after its domain—purchased via Google Cloud Domains API—ended up under Squarespace Domains II LLC as the official ICANN registrar. Despite the domain expiring and Squarespace being the sole party consistently emailing renewal notices, the provider claims renewal must occur through Google Cloud. Google Cloud’s support channels are not accessible to past customers without paid plans, and Squarespace’s guidance is unworkable. The domain is currently offline, impacting business operations, and a formal demand has been issued.
What happened in detail
– Setup and contractual relationship: The company registered a domain through Google Cloud Domains API within a dedicated Google Cloud project. During registration, terms were accepted that referenced the Squarespace Domain Registration Agreement, establishing Squarespace as the registrar through which the domain would be managed.
– The problem arises now: The domain expired. The associated Google Cloud project has been closed for some time, and there is no available path to renew via Google Cloud’s interfaces.
– The renewal cycle and dead ends: When attempting renewed management with Squarespace, the response has consistently been that renewal must be processed through Google Cloud. The business contends that Squarespace is the registrar of record per ICANN WHOIS, and thus Squarespace should handle renewal.
– Anomalous communications: Squarespace is the only vendor that has emailed the company about the domain’s lifecycle, including renewal notices. Their position conflicts with their own communications that imply Google Cloud is responsible.
– Escalation and outcome: After escalation to Squarespace’s Trust & Safety, the final reply again redirects to Google Cloud.
– The insurmountable hurdle with Google Cloud:
– No free support for past customers; Google Cloud’s support options are oriented toward current, paying customers or sales inquiries.
– To obtain any support, the company would need to purchase a new Basic Support plan, approximately $30–$40 per month.
– The link provided by Squarespace to guide the user (cloud.google.com/contact) is broken and returns a service-unavailable page.
– Current status: The domain is offline. Squarespace, as the registrar, is not performing its basic function and directs the user down an impractical, costly path with a broken link.
What the user is seeking
– A 72-hour deadline to obtain a direct renewal invoice.
– If renewal is not resolved, potential legal action, a formal registrar complaint to ICANN, and complaints to consumer protection agencies.
– Guidance on:
– Whether others have experienced this renewal impasse when the domain was purchased via Google Cloud API and registered with Squarespace.
– The ICANN Registrar Complaint process and tips for effectiveness and timely responses.
– Any additional steps or leverage points (executive outreach, social media, etc.).
– Recommendations for a competent, no-nonsense registrar to transfer the domain and other domains to once resolved.
Key questions for readers or experts
– Has anyone else encountered a renewal stalemate with a domain purchased through the Google Cloud API that ends up under Squarespace as the registrar?
– What has been your experience with ICANN Registrar Complaints in cases like this? Any tactics to speed up responses or escalation?
– Are there other pressure points or escalation strategies that are appropriate and legally sound?
– After securing resolution, which registrars are reliable and straightforward for transferring domains from Squarespace and Google Cloud-backed registrations?
Takeaways and potential paths forward
– Clarify registrar of record: Verify the current ICANN Whois data to determine the designated registrar and the applicable contact point for renewal and administrative updates.
– Document communications: Gather all renewal notices and communications from Squarespace and any attempts to contact Google Cloud, noting dates and content.
– Consider formal avenues: If renewal cannot be completed in a reasonable timeframe, a registrar-should-be-responsible path via ICANN, along with consumer protection filings, may be warranted.
– Evaluate transfer options: If possible, prepare for a registrar-to-registrar transfer to a reputable provider to regain control and ensure ongoing renewalability without reliance on a single vendor’s customer support channels.
Note: If you’re reading this and have direct experience with Squarespace as a registrar, or with Google Cloud Domains API registrations that converted to Squarespace, your insights could be highly valuable. Similarly, guidance on ICANN registrar complaint procedures and the typical timelines you’ve observed would be greatly appreciated.
