Internet Corporation for Assigned Names and Numbers

John L. Crain | Chief Security, Stability and Resiliency Officer

John is responsible for establishing strategy, planning and execution for ICANN's external Security, Stability and Resiliency programs. He works on a cross functional basis with the ICANN executive team, staff and the community to enable and enhance capabilities that improve the overall security, stability and resiliency of the Internet's Identifier Systems and associated infrastructures and represents ICANN in operational and technical dialogues and forums to ensure the full communities engagement with these programs.

The Internet Corporation for Assigned Names and Numbers (ICANN) is an internationally organized, non-profit corporation that has responsibility for Internet Protocol (IP) address space allocation, protocol identifier assignment, generic (gTLD) and country code (ccTLD) Top-Level Domain name system management, and root server system management functions.

Prior to his time at ICANN, John worked as part of the executive management team at the RIPE NCC in Amsterdam (http://www.ripe.net). The RIPE NCC is the Regional Internet Registry (RIR) that provides Internet resource allocations for Europe and surrounding areas. John has been directly involved in the administration of Internet Identifiers since his start at the RIPE NCC in 1995 and has worked in all areas of IP address administration. John also has extensive experience in the area of DNS administration and managing Internet infrastructure services. Currently he is responsible for the management of l.root-servers.net, one of the Internet’s 13 “Root Servers” (http://www.root-servers.org)

Before becoming involved in Internet Administration John worked as a Design Engineer in composite materials research and development. In that role John was also responsible for local area networking of Computer Aided Design Systems and for writing and developing custom software applications.

Stay Connected

  • News Alerts:
  • Newsletter:
  • Compliance Newsletter:
  • Policy Update: