blocks|key|1847838|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|-4|4|5|6|B|7|@]|8|@]|9|$]]]|A|$]]

The subject of your question is complicated, and can not be resumed in a few sentences.

In summary, GDPR is still new to many entities, and there is still some phases of adaptation. ICANN (who controls what gTLDs can or can not do) took a lot of time to accept that GDPR won't go away and had to finally take it into account. It created a "temporary specification" for which you can get details at <a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en" rel="nofollow noreferrer">https://www.icann.org/resources/pages/gtld-registration-data-specs-en</a>. Which is why, for now, if you look at any gTLD registry whois reply, you will mostly see no personal data, no more emails, names, addresses, etc. But this is "temporary". Of course not everyone is happy with that: LEAs, IP lawyers and others want very much to go back to the old model... It may (it will) appear in fact, because whois will slowly be phased out by RDAP (which is mandatory in the gTLD world since August 2018), and RDAP being built on a saner design, can allow (where whois couldn't) far more easily to put tiered access, that is to have an authentication layer and hence change the amount of results given (with or without personal data, and how much) depending on who queries. But we are far from a working model on that stage.

For ccTLDs, each registry has to decide what to do, things are not clear cut. You will find some that err towards the side of "let us not show anything, or almost anything at all", for example <code>.de</code> (you do not even see the registration date anymore...), and then others do completely the opposite, like <code>.IS</code> (<a href="http://domainincite.com/22939-iceland-breaks-ranks-on-whois-will-publish-emails" rel="nofollow noreferrer">http://domainincite.com/22939-iceland-breaks-ranks-on-whois-will-publish-emails</a> : "Iceland’s ccTLD has become what I believe is the first registry to state that it will continue to publish email addresses in public Whois records after the General Data Protection Regulation comes into effect.")

So you can find various articles explaining how the GDPR killed whois, such as:

<ul>
<li><a href="https://www.forbes.com/sites/davelewis/2017/12/21/whois-the-first-casualty-of-gdpr/" rel="nofollow noreferrer">WHOIS The First Casualty Of GDPR?</a></li>
<li><a href="https://domainnamewire.com/2017/08/17/gdpr-whois/" rel="nofollow noreferrer">Will May 2018 be the death of Whois?</a></li>
<li><a href="http://domainincite.com/23053-how-all-33-european-cctlds-are-handling-gdpr" rel="nofollow noreferrer">How all 33 European ccTLDs are handling GDPR</a></li>
</ul>

Now you raise another important point about "privacy products" from some registrars.

In many (but not all) TLDs, and at least in gTLDs, you have a registry/registrar model: one registry, multiple registrars.

A customer goes to one registrar, gives it all its data (including personal one, and paying for the domain), the registrar stores it locally, also sends it or part of it to the registry, that stores it on its side.

This model may then has the consequence (at least because ICANN decided so, but there is mostly no technical reason for that, as the last thin registry in gTLD world will "soon" be thick like all the others) that there is in fact two whois servers (or RDAP ones for that matter) for a given domain name: one at registry side, one at registrar side.

Of course each server replies with data that is stored locally, but that explains why each one may not answer with the same data.
Because if you take/buy some registrar (or third party) "privacy" service here is what happens:

<ul>
<li>you give your personal data to the registrar; it is stored in its database</li>
<li>the registrar sends to the registry ANOTHER set of personal data, a blank "privacy" one; in that way of doing things, the registry never sees the "real" data (which has its own set of consequences, because with that the registry can not even know who is the real registrant)</li>
<li>so if you query the registry whois/RDAP server you will get "privacy" data at most and not the real one,</li>
<li>and if you contact the registrar whois/RDAP server, while technically it has locally the real data, because you enabled that privacy service, the registrar will reply with this privacy data instead of the real one.</li>
</ul>

And then as said above, on top of a given set of data that should have been given, recent changes due to GDPR, "scrub" the data and basically creates almost empty results.

This is indeed something to take into account if you want to transfer domains between registrars. A previous ICANN rule for example, in gTLDs, mandated registrars to get formal and explicitly positive acknowledgment (through some specific emails called FOA for Form Of Authorization) from registrant/admin contact before being able to go forward with a transfer request. This data was mostly taken out of whois by registrars, but of course now that the whois reply is almost devoid of substance, this can not work anymore (and hence transfers go back to their previous model were the sole possession of the "authInfo" value for the domain was enough to prove ownership of it and hence start transfers).

Typically registrars will ask you to provide new contact data if you decide to do a transfer as they won't be able to collect it from current setup. When a transfer happens, nothing changes at the registry level, except who is the registrar. As soon as the transfer completes, the new registrar is (mostly) free to change all data, including contacts (but see new ICANN regulations that treat a registrant change mostly the same as a registrar change, with various checks and periods), and then apply again, or not (depending on what the registrar provides and what the customers chose) some privacy service as explained above.

Going back to:

<blockquote>
 I live in the Netherlands and have a .com domain at Namecheap. According to the Namecheap support, my data becomes public in Who is if I disable their Who is Guard.
</blockquote>

Specifically in .COM, this is still a thin registry, which means the registry DOES NOT have the contact data (the registrar NEVER sends it to the registry). This will change, it is planned (but postponed more than once, the issue is obviously intertwined with everything discussed previously), but it is like that today. So if you do a whois query for a .COM at the registry you will never see contact data, no matter what service you enable or disable at the registrar level because the registry has no contact data at all for the domain.

Now at the registrar level, they are "free" to do what they want, I mean they can have their own interpretation of GDPR, how much it applies to them or not, etc.

At least on one of their page they say this:

<blockquote>
 When you register a domain, ICANN requires registrars to provide them
 with your contact information (such as name, email, address, and phone
 number). This is then added to the Whois database. This database lists
 the owners of every domain name online, and it can be searched by
 anyone on the Internet.
</blockquote>

It is not very clear to me or maybe slightly wrong: I do not know who is "them" in first sentence, but if that is meant to be ICANN then it is completely wrong, ICANN has no operational role in day to day registrations, so they have no data. Also there is no "Whois database" even if everyone makes this error. whois is a protocol to query data. The database queried by it sits at a registry or registrar, and is not a "whois database" in the same way that you use HTTP to contact webservers but that does not make websites suddenly "HTTP databases".
But even outside of that, it can not really be "searched". whois is a query protocol (RDAP too, and has extensions for real search capabilities but it is yet to happen for anyone to implement that for obvious technical and non technical consequences of that), you ask details about a specific domain. You can not ask details about a specific registrant name, or address or phone numbers or whatever. There are various services online providing such kind of "reverse searches" (like: give me the list of domain names owned by "Foo Bar Inc."), and how they do it? They do whois queries, store results (in a "database" also), and hence can provide searches in it, but with various limitations (whois is ratelimited, their data will never be fresh, multiple TLDs are against that, see <a href="https://www.domainpulse.com/2019/06/25/domaintools-appeals-to-seek-to-continue-flouting-nz-whois-terms-of-use/" rel="nofollow noreferrer">https://www.domainpulse.com/2019/06/25/domaintools-appeals-to-seek-to-continue-flouting-nz-whois-terms-of-use/</a>, etc.)

So I have no idea what happens if you do not use "WhoisGuard". Your provider should be able to clearly explain the situation for you, and if not or if you are not happy with its answer, it will certainly be a good time to shop around for another one.

Exactly how does it work with GDPR and Who is? I live in the Netherlands and have a .com domain at Namecheap. According to the Namecheap support, my data becomes public in Who is if I disable their Who is Guard. However, I read online that Who is data of EU citizens will not be made public How does this work?
I know that Who is Guard is nowadays free at Namecheap, but I'm curious. This can also be useful to know if I ever want to transfer my domain to another registrar.

Confused about GDPR and Who is

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

它到底是如何与探地雷达一起工作的?谁是？我住在荷兰，在Namec堆有一个.com域名。根据Namec堆支持，如果我禁用了他们的their，我的数据就会被公开。然而，我在网上读到，欧盟公民的数据将不会公诸于众，这是如何运作的呢？我知道现在谁是卫兵是免费的，但我很好奇。这也可能是有用的，如果我想要转移我的域名到另一个登记员。

问对探地雷达和谁是
EN

回答 1

Webmasters Stack Exchange用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对探地雷达和谁是EN