Skip to content
Tuesday, October 20, 2026AboutContactRSS
Privacy & Policy

ICANN tests single sign-on for law enforcement WHOIS access

A new authentication framework aims to let police request private domain data for urgent safety threats, with registrar support.

Illustration: A sleek black keyboard sits on a clean white desk beside a modern smartphone.
AI-generated illustration: Threat Times

Key points

  • ICANN is testing authentication schemes for law enforcement to access non-public WHOIS data.
  • The mechanism targets imminent threats to life, critical infrastructure, or child exploitation.
  • Registrars Namecheap and Verisign expressed support for the technical proposal during ICANN's Bali meeting.

ICANN has begun testing authentication methods that permit law enforcement agencies to submit urgent requests for non-public WHOIS information. This development was announced during the organization’s annual meeting in Bali, Indonesia, where an input group detailed the progress of the new access mechanisms.

The proposed system utilizes single sign-on technology to facilitate these requests. The goal is to address situations involving imminent threats to human life, serious bodily injury, critical infrastructure, or child exploitation. Currently, registrars hold customer data that was once public but is now often shielded by privacy laws like GDPR or privacy proxy services.

Technical and Policy Context

The Input Group on Law Enforcement Agency Authentication Mechanisms focused its recent work on the technical aspects of identity verification. According to The Register, the group’s current mandate is largely engineering-focused, ensuring that a robust technical mechanism exists for validating requests. Policy groups within ICANN will subsequently determine acceptable use cases and related governance issues.

This separation of technical and policy work reflects standard internet governance procedures. Specialists address specific components of a problem before collaborating to create a system that is technically sound, practical, and enforceable across multiple jurisdictions. The technical foundation must be established before broader policy debates on access controls can proceed effectively.

Industry Reception and Concerns

Domain industry representatives have engaged with the proposal, offering a mix of support and caution. Namecheap and Verisign spoke during the session at the Bali meeting, and both organizations indicated support for the initiative. Their involvement suggests that major registrars see value in a standardized, secure method for handling urgent law enforcement inquiries.

However, observers may worry that such a mechanism could enable inappropriate or excessive requests for private data. The current framework limits access to specific, high-severity scenarios defined by ICANN. By restricting the scope to immediate dangers like child exploitation or critical infrastructure attacks, the system aims to balance privacy protections with public safety needs. The technical nature of the current phase keeps the focus on secure authentication rather than broad data access.

What should you do?

Security and technology professionals should monitor ICANN announcements for formal policy ratifications. Organizations that operate domain registries or provide registrar services should prepare for potential integration requirements. Law enforcement agencies may need to update their procedures for requesting digital evidence as these technical standards mature.

What to do and how to stay safe: ICANN

  • Review internal policies regarding domain registration and privacy protection services to ensure compliance with emerging standards.
  • Monitor ICANN public comment periods for the policy groups that will define acceptable use cases for the new authentication mechanism.
  • Ensure that incident response plans include procedures for handling urgent requests related to critical infrastructure or child exploitation.
  • Stay informed about GDPR and other privacy regulations that may interact with these new law enforcement access protocols.

Step-by-step guide: How to Remove Data from Data Brokers: The Manual Cleanup Process

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Can law enforcement access WHOIS data for any reason now?

No, the proposal restricts access to imminent threats to life, serious bodily injury, critical infrastructure, or child exploitation.

Have all registrars agreed to this new system?

Namecheap and Verisign expressed support during the meeting, but the mechanism is still in the testing phase.

Is the policy for using this data finalized?

No, ICANN policy groups will work out acceptable use and related issues after the technical mechanism is devised.

Sources

  1. The Register
ICANNWHOISNamecheapVerisignGDPR
Related articles