| Nov 10, 2016 | How Workstream 2 Plans to Improve ICANN's Transparency |
| Nov 03, 2016 | If the DIDP Did Its Job |
| Jul 30, 2016 | DIDP Request #20 - Is Presumptive Renewal of Verisign’s Contracts a Good Thing? |
| Jul 30, 2016 | DIDP Request #21 - ICANN’s Relationship with the RIRs |
| Jul 30, 2016 | DIDP Request #22 - Reconsideration Requests from Parties affected by ICANN Action |
| Jul 30, 2016 | DIDP Request #23 - ICANN does not Know how Diverse its Comment Section Is |
| Jul 30, 2016 | DIDP Request #25 - Curbing Sexual Harassment at ICANN |
| Jul 30, 2016 | DIDP Request #27 - On ICANN’s support to new gTLD Applicants |
| Jul 30, 2016 | DIDP Request #28 - ICANN renews Verisign’s RZM Contract? |
| Jul 29, 2016 | DIDP Request #15: What is going on between Verisign and ICANN? |
| Jul 29, 2016 | DIDP Request #16 - ICANN has no Documentation on Registrars’ “Abuse Contacts” |
| Jul 29, 2016 | DIDP Request #17 - How ICANN Chooses their Contractual Compliance Auditors |
| Jul 29, 2016 | DIDP Request #18 - ICANN’s Internal Website will Stay Internal |
| Jul 29, 2016 | DIDP Request #19 - ICANN’s role in the Postponement of the IANA Transition |
| Jul 28, 2016 | DIDP Request #13: Keeping track of ICANN’s contracted parties: Registries |
| Jul 28, 2016 | DIDP Request #14: Keeping track of ICANN’s contracted parties: Registrars |
| Jul 27, 2016 | DIDP Request #10 - ICANN does not know how much each RIR contributes to its Budget |
| Jul 27, 2016 | DIDP Request #9 - Exactly how involved is ICANN in the NETmundial Initiative? |
