Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Mike Easter Newsgroups: alt.os.linux.mageia Subject: Re: WHOIS is being replaced ...? Date: Tue, 6 Jan 2026 10:49:13 -0800 Lines: 23 Message-ID: References: <10i1jd2$kccd$1@dont-email.me> <10jj3gu$1b5d4$1@paganini.bofh.team> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net RDflfeMcDQwwRC3dHBq1KQ9AGc890b6s+GxMsHb+2ojp0lqTjR Cancel-Lock: sha1:hvlm/uoDTksqQSFak4NyooQwzbU= sha256:ohPkq/+U/yPaOmKrb/SO7PjSsCVECzZEln7CUBTvUN8= User-Agent: Mozilla Thunderbird Content-Language: en-US In-Reply-To: Xref: csiph.com alt.os.linux.mageia:28038 Mike Easter wrote: > > Your link is about the availability of a web-based rdap function. > > There is also an openrdap site here: > https://www.openrdap.org/ > Now that I'm 'getting into' this, there is an interesting 'back story' (I LUV b/s) in its wp article about the problems w/ the development and the implementation, which has been going on for years. https://en.wikipedia.org/wiki/Registration_Data_Access_Protocol Things are still somewhat incomplete because of what might be considered the 'complexity' (not TOO bad) as well as the 'compliance' (limited to recency). > For name registries, ICANN requires RDAP compliance since 2013. -- Mike Easter