In this particular case, one needs to go to name.com website and request whois, which is not 100% natural thing to do for .pro. Afaik the only thin registries are .com, .net and .jobs. Dot pro is thick registry and normal registry whois output is GDRP-compliant:
Domain Name: RUSSELL.PRO
Registry Domain ID: D503300000114523791-LRMS
Registrar WHOIS Server: whois.name.com
Registrar URL:
www.name.com
Updated Date: 2018-07-06T14:43:11Z
Creation Date: 2018-07-06T14:43:09Z
Registry Expiry Date: 2019-07-06T14:43:09Z
Registrar Registration Expiration Date:
Registrar: Name.com LLC
Registrar IANA ID: 625
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientTransferProhibited
https://icann.org/epp#clientTransferProhibited
Domain Status: serverTransferProhibited
https://icann.org/epp#serverTransferProhibited
Domain Status: addPeriod
https://icann.org/epp#addPeriod
Registrant Organization: China Dior Industrial Co., Ltd.
Registrant State/Province: TP
Registrant Country: TW
Name Server: NS1.PARKINGCREW.NET
Name Server: NS2.PARKINGCREW.NET
Why name.com registrar elected to serve web-based whois requests from their local db and in non-GDRP compliant way is an interesting question.