Please release cryptocardcodes.com - domain held by a site on a team I can no longer access

Support
1

Hi Netlify support,

I own the domain cryptocardcodes.com (registered at Spaceship, currently using Spaceship nameservers). It is still held by a site on an older Netlify team that I can no longer sign in to, so I cannot release it from that side.

Details:

  • My current project: cryptocardcodes - https://cryptocardcodes.netlify.app - site ID 22238e2a-e575-4b13-8939-cef5e81c99c0, on the Free team belonging to the same account I used to log in to these forums.
  • Blocking site ID: 34713cc0-3b53-4340-8b67-6e7c9bd4baa8. That team’s account is suspended, so I cannot remove the domain or delete its DNS zone. I can send you that account’s email privately if you need it for verification.

Attaching the domain to my current project fails with:

"custom_domain": ["is owned by another account",
"must be unique (cryptocardcodes.com, 34713cc0-3b53-4340-8b67-6e7c9bd4baa8)"]

I get the same error for www.cryptocardcodes.com and for any other subdomain I try (for example go.cryptocardcodes.com), so the entire zone appears to be held by that site.

Could you please release cryptocardcodes.com and its subdomains, and remove the orphaned Netlify DNS zone, so I can add the domain to my current project?

I control DNS at the registrar and can add any verification record you need. If a verified-for-netlify TXT record containing this thread URL is the right proof of ownership, please confirm and I will add it immediately.

Thank you.

2

Update: the ownership proof record is already live.

verified-for-netlify.cryptocardcodes.com. TXT "https://answers.netlify.com/t/please-release-cryptocardcodes-com-domain-held-by-a-site-on-a-team-i-can-no-longer-access/167611"

It resolves publicly from the authoritative Spaceship nameservers and from 8.8.8.8. Happy to add or change any other record you need.

The apex and www are currently pointed at a temporary registrar-level redirect to https://cryptocardcodes.netlify.app so the site stays reachable. I will remove that redirect and point DNS wherever you advise as soon as the domain is released.