Streamlining domain name abuse reports and disclosure requests

We released a few new features, one of them, RDAP reseller Vcard. 

To further streamline abuse reports & disclosure requests, Realtime Register introduces the Abuse Vcard. This Vcard will display your (reseller role) abuse contact details through RDAP. 

Showing your (external) abuse contact information will increase the speed of abuse reporting. 

Internal abuse email address/information. 

Resellers can also enter abuse contact information for our abuse & support staff. 

We are not setting requirements here for our resellers, but it would be good if this email address is monitored 24/7. We intend to use this info for emergency communications when dealing with security threats. 

Abuse Domain Manager

 

External abuse reporting address (RDAP). 

RDAP, the replacement of WHOIS, is role-based and supports Vcards. The general idea is that resellers supply their public abuse email address and Company name and telephone number. 

Once this information is present in our system, we will display the info through RDAP. We are confident that the use of this extra contact will streamline abuse reporting.  

Resellers can also assign an abuse contact information for sub-resellers or different labels using the branding management tool within the reseller account. 

At a later stage, we will incorporate such public abuse email addresses in our reseller lookup tool. 

Reseller lookup tool? Yes, just before the GDPR enforcement back in 2018, we introduced a reseller lookup tool to assist LEA’s and other third parties. 

https://www.realtimeregister.com/resources/locate-your-provider/

Reseller Lookup tool

For the reader who knows RDAP very well, yes, we are using the reseller role to display abuse contact information. 

We think that this a better use for now as we already have a reseller lookup tool. 

While RDAP supports many more roles, there is currently no standard for other roles. Once more roles are defined, we can add more info to RDAP. 

Data Protection Officer 

If your company has a DPO, please enter their contact information. While this would satisfy GDPR compliance requirements, there are multiple practical reasons: 

  • Registrant disclosure requests
  • More streamlined communication if there is a data breach. 
  • Improved communication if a data subject wants to exercise his or her rights provided by the GDPR. 

RDAP Output with Abuse Vcard

ICANN SSAD.

The ICANN community is still working on the Standardized System for Access and Disclosure (SSAD).

The details of how this is going to work are still being discussed.

 But we imagine that at some point, we want to automate disclosure requests as much as possible. 

The DPO contact role may, at some point, be used within the SSAD to send disclosure requests.

GDPR Art 27

For those of our resellers who need to comply with Art 27, you can now enter an email address of such a GDPR Representative.

Again this is to ensure better coordination between requestors and other third parties. 

The GDPR Representative data is not public in the WHOIS or RDAP. 

Please check our knowledge base on how to add this information to your into the Realtime Register Domain Manager.