search

wabisabi-js / isthereuber.in

Simple app to tell you where there is uber
https://isthereuber.in
MIT License
150 stars 37 forks source link

.in registry prohibits privacy protect #87

Open rootkea opened 2 years ago

rootkea commented 2 years ago

3. Proxy/Privacy Services: Any kind of proxy services are not allowed, and if the data is wrong or masked out by any proxy/ privilege protection services, the Registrant shall not be recognized as the owner of the domain name.

Source: https://www.registry.in/system/files/Terms_and_Conditions_for_Registrants_1_0.pdf

rootkea commented 2 years ago

I suggest we move to privacy protect friendly registry or else the current .in domain might get seized/closed.

Fortunately only handful of the registries are not privacy protect friendly. Rest of them are.

Many registrars maintain the explicit list of tlds whose registries don't support privacy protect.

  1. Namecheap "Due to registry restrictions, WhoisGuard cannot be used with .ca, .ch, .cn, .co.uk, .com.au, .com.es, .com.sg, .de, .es, .eu, .fr, .gg, .id, .in, .is, .li, .me.uk, .net.au, .nom.es, .nu, .nyc, .org.es, .org.au, .org.uk, .paris, .sg, .to, .uk, .us, .vote, .voto, .xn--3ds443g domains."
  2. Dynadot
  3. Name.com etc.

You can also use this Google domains reference to confirm whether the tld you are interested is from the privacy protect friendly registry or not. Just select the TLD and check "Allows WHOIS privacy"