3 ms·
A public (historical) WHOIS dataset is a nightmare due to GDPR et al., though, isn't it? You couldn't opt-out of WHOIS (some TLDs just didn't allow for WHOIS p
by schroeding 4y ago
A public (historical) WHOIS dataset is a nightmare due to GDPR et al., though, isn't it?
You couldn't opt-out of WHOIS (some TLDs just didn't allow for WHOIS privacy / proxy registrations) in the past, and it's IMO quite a hard sell that the public interest in the historic WHOIS data of some personal website should have any weight at all in this case.
- posterboy 4y agoThat's an interesting way to put it. There is some interest, no doubt, and there is some potential abusing that information. Since the information was committed knowingly and willingly to the public domain, though I do not know much about it to begin with, I don't see how GDPR applies at all.
- schroeding 4y agoThe GDPR allows you to force companies to delete data that was knowingly and willingly commited, though, via article 21 and 17c GDPR [1], except if there are "overriding legitimate grounds for the processing" of the data. I doubt there are, at least for low-profile, personal websites and historical WHOIS data. You could IMO also make an argument that the collection and scraping of WHOIS data without consent was unlawful processing as a whole, as the data was not provided to the domain NIC with explicit consent for third-parties to collect and save them forever, which would even make any overriding legitimate grounds for processing moot. 17a may also apply: The reason for WHOIS is to find out who owns a domain now, right? There is no version history. Historical WHOIS data does not serve this purpose anymore. It's quite the can of worms. [1] https://gdpr-text.com/de/read/article-17/ https://gdpr-text.com/de/read/article-17/