Resolve the greta website issue

Pointing Claude at this, it looks like this is something only @goldingn can resolve currently, and it looks like it is doable on netlify. I remember doing something similar to this at some point when netlify changed some processes. Here's what Claude says - hope it is helpful!

- greta-stats.org resolves to 54.253.94.210 — an AWS Sydney IP, not Netlify's current anycast endpoint (75.2.60.5). That's a stale A record.
- The endpoint answers with Server: Netlify but presents a *.netlify.app TLS cert → hostname mismatch → browsers hard-fail HTTPS.
- Meaning: Netlify has not provisioned a Let's Encrypt cert for greta-stats.org. That happens when the custom domain isn't verified on the site and/or DNS doesn't point where Netlify expects. It's then serving the old Bootstrap-3 site from the repo's docs/ folder.

The fix (for whoever has access): in Netlify → Domain management, (re)add & verify greta-stats.org; at NS1, repoint the apex to Netlify's current target (ALIAS/A to 75.2.60.5, remove the stale 54.253.94.210); let Netlify re-issue the cert.

Start in Netlify Domain management and the NS1 DNS settings described in the issue; verify the current apex record and custom-domain status. Done means greta-stats.org points to Netlify's current target, the site serves the expected hostname, and HTTPS presents a valid certificate.

Written by the indexing model from the issue text.