| Service | Address | Record state |
|---|---|---|
| policy | https://www.registry.google/policies/pricing/eat/ | current |
| policy | https://www.registry.google/policies/registration/eat/ | current |
| policy | https://www.registry.google/policies/startup/eat/ | current |
| rdap | https://pubapi.registry.google/rdap/ | current |
| website | https://www.registry.google/ | current |
| Nameserver | IPv4 | IPv6 | Address evidence |
|---|---|---|---|
| ns-tld1.charlestonroadregistry.com | 216.239.32.105 | 2001:4860:4802:32::69 | Published addresses |
| ns-tld2.charlestonroadregistry.com | 216.239.34.105 | 2001:4860:4802:34::69 | Published addresses |
| ns-tld3.charlestonroadregistry.com | 216.239.36.105 | 2001:4860:4802:36::69 | Published addresses |
| ns-tld4.charlestonroadregistry.com | 216.239.38.105 | 2001:4860:4802:38::69 | Published addresses |
| ns-tld5.charlestonroadregistry.com | 216.239.60.105 | 2001:4860:4805::69 | Published addresses |
Search a specific .eat name to check availability and use the technical page for documented eligibility rules. A seller’s standard price does not decide whether an applicant or a particular name qualifies.
Yes. The root delegation for .eat has a published DS record. That is not evidence that a registrar can submit DS records for an individual domain.
The registry record currently does not establish every policy or syntax field for .eat. Missing evidence is shown as unknown rather than treated as permission, a restriction, or a DNSSEC capability.