Last week we received a lot of positive comments regarding our GDPR TLD matrix. And we had a lot of requests to get access to the matrix.
As a push to create more GDPR awareness, we decided to publish our API on the website for the public, including the GDPR TLD matrix.
You can enter the matrix here.
Keep in mind the matrix has been developed with the Realtime Register processes in mind and in some instances cannot be merely be pasted and copied.
One comment which we received a lot last week was:”wow there are so many …
I think this is the first blog where I start with phrases like;
- We are not done yet
- Guidance only
- We are not done yet
- By no means legal advise
- Best effort only
- We are not done yet
While we are not done, we are trying to get this matrix as complete as possible before May 25; we do expect that we will still be updating the matrix way beyond May 25.
Back in 2016, I was under the impression that our industry would work together and come up with solutions to make things easier when it comes to the …
Just before ICANN 61, ICANN and its community received essential information regarding WHOIS and the GDPR and more.
The latest statement and recommendations are from the Berlin Group (International Working Group on Data Protection in Telecommunications and Media or IWGDPT).
The Berlin Group started out in 1983 on the initiative of some national data protection authorities; nowadays members include government agencies, representatives of international organizations and IT experts from all over the world.
So basically we have the opinion on ICANN and registrant data and WHOIS vetted by all the members of the International Conference of Data Protection and Privacy …
Kevin Murphy from DomainIncite has written an excellent article about the all the ins and outs how WHOIS might look like in May this year, which you can read here.
I do not entirely agree with Kevin if privacy services are going to be free.
In the current setup, our privacy proxy service still has added value when it comes to spam prevention.
I think it is more accurate, that if ICANN no longer requires personal data to be displayed in the WHOIS the need use a privacy service to prevent such display of personal data becomes obsolete, after …
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 …
There has been a considerable debate whatever ICANN will enforce the contractual agreement between registrars and registries to display personal data in the WHOIS.
Publication of personal data in the WHOIS is usually in conflict with many data protection laws around the world.
The EU GDPR and its substantial non-compliance fines seem to sway the discussion into a direction where ICANN needs to come up with solutions. And they did: ICANN published several models that propose to limit the publication of personal data in the WHOIS. The next step is that the ICANN community analyzes these models.
The models created …
Below, a quick update and some information which is crucial to you as a reseller regarding the GDPR.
Privacy notice
We should have the privacy notice ready for you at the end of February.
Processing agreement
We expect to send this to our resellers at the end of February, given the vast amount of different jurisdictions and number of registries this may be delayed by a few weeks.
The processing agreement is required for your contractual agreements between you and our customers.
Legal definitions
- ICANN, joint data controller
- gTLD registries, joint data controller
- ccTLD registries, data controller
- Realtime Register (registrar), …
Domain names, registrant data and data protection, they all have a long history in the ICANN universe. Let’s do some time traveling and let me take you back in time, starting a decade ago…
March 2007
ICANN de-accredits RegistryFly, this disaster demonstrates clearly that Registrars should escrow registrant data to an escrow provider in case a registrar goes “down.”
To counter the RegistryFly disaster, ICANN introduced escrow requirements, ICANN picks up the bill, but of course, indirectly the registrars are paying for it, how much is unknown though, as we do not know how much ICANN is paying Iron …
Companies will face very harsh punishments for infringements under the GDPR. Art. 83 Paragraph 5 of the GDPR offers the supervising authorities the possibility of imposing fines of up to 20 million Euro or, for corporations, up to 4% of the worldwide turnover of the preceding financial year.
Tick tock, tick tock, goes the clock
The EU GDPR will go into effect May 25th, 2018. It looks like there is still a lot of time, but actually, there is not much time left to prep your organization for the GDPR!
Most of your company’s operations will be affected by …
This page is dedicated to the relevant changes, added features and fixes of the Realtime Register front and back end. Please visit regularly to stay up to speed. The API Changes are documented in more detail on the API Docs Change Log pages and additional documentation. Please note, login is required.
26/09/2017
Improvement: Privacy Protect v2 allows transfer out without exposing registrants date. In preparation for GDPR.
Bugfix: Denic, some unsupported Unicode characters in address contacts will now give the proper error message.
Improvement: NicIT, NS check now inline with registry policy.
Improvement: NicIT, Client hold option removed.
Bugfix: …