APNIC participated at bdNOG 7 in Dhaka, Bangladesh from 18 to 22 November 2017.
LEAs are important members of the APNIC community working towards a safer and more secure Internet.
APNIC has resolved a whois security incident resulting from a technical error during the upgrade of APNIC’s whois database.
As of 31 August 2017, 42% of APNIC Members have reviewed their organization contact details.
The traffic on the public whois service at APNIC continues unabated, but there is a far simpler, better way to query the same information: RDAP.
The APNIC whowas service provides visibility into prior states of APNIC resource registration records.
New whois features will be available in the coming months when the APNIC whois master server update is complete.
Geoff Huston examines the policy proposals discussed at ARIN 39, including those dealing with whois database curation and IPv4 transfers.
APNIC has begun developing a new set of application programming interfaces (APIs) for Members and we want your feedback.
Guest Post: EUROPOL’s Grégory Mounier argues that more detailed policy is required to address whois inaccuracy problems.