Privacy by default account setting.

Today we introduce a new account setting called:”Default Privacy Protect setting”, which you can access by clicking here.

Setting disabled.

When selected, domain name registrations and transfers will not use our privacy service automatically. This is how it used to work for years.

Setting enabled when free (and available)

When enabled all domain name registrations and transfers will automatically use our privacy service. Regardless if you use WHMCS, our API or the domain name manager.

A list of available TLDs that can be used for this service is located here.

We keep recommending this service as it is unknown if gTLD registries will continue to publish the data in the WHOIS or not. Several large gTLDs will no longer publish the WHOIS, similar to how we will operate our WHOIS server. But some of them most likely will keep publishing registrant data.

Enabled (when available)

Same as above but also will use privacy services that are not free of charge. Please check the price list in your account if that is the case.

Registration

When you register a domain name you can override your account settings if required. Select the desired action from the drop-down menu.

Current Customers.

At the moment the default setting is not active, as mentioned earlier. Due to the new ICANN contractual regulations that have been rushed out of the door on 17-05-2018 this week, we are reviewing the option to turn this on for all customers. I apologize in advance for any inconvenience this may cause.

ICANN Registrars express GDPR concerns to ICANN

Today the Registrar Stakeholder Group (RrSG) has joined its colleagues in the Registry Stakeholder Group, Eco Association of the Internet Industry and the Internet Infrastructure Coalition in raising its concerns with ICANN about GDPR.

The letter was drafted last week and got so much support from the registrar members that we could officially support it as a stakeholder group. Realtime Register B.V. was one of the supporters.

The letter to the ICANN CEO located here,┬ácan be described as “spicy,” or “\strong.” And I think it is with good reason. Since March 2016 a dedicated small group of registrars and registries have been pouring countless of hours of time in supporting ICANN with this complex issue called the GDPR, I cannot recall how many telephone conferences I had since March 2017 till this very day, but most likely an insane number for sure.

The problem?

ICANN contractual obligations force registries and registrars to publish the personal data in a public directory called the WHOIS. The GDPR does not allow data being used beyond its original purpose, which is the registration of the domain name.
When you order a product online; you provide the shop with information so they can deliver/ship your product. It is not up to the shop to publish all your data in a public directory and mention what product you purchased. You rather not have such data released for obvious reasons, not the whole world has to know what you bought last weekend, right?
This example I guess, highlights the entire issue with the WHOIS and the tension it creates with many data protection and privacy laws.

I understand if this letter might come on strong for some folks at the ICANN organization and perhaps some stakeholders within the ICANN community, but it is ten minutes to midnight for sure, and as contracted parties, we are all liable when it comes to the GDPR, and its massive fines, and not the ICANN community. Every hour we delay will cause more issues for us registrars and our customers.

Lucky enough a significant deal of the GDPR issues can be mitigated with the free Realtime Register privacy proxy services. And while that is convenient for our customers, not every registrar offers these services and as such, are entirely depended on solutions created by ICANN.

More information regarding our privacy services can be read here.