Summary
IANA says Ceremony 62 is complete.
- The ceremony began at 20:00 UTC on 12 August.
- Its listed objectives were to sign 2026Q4 ZSKs and destroy HSMs 5W and 6W.
- The page provides a rewatch archive.
- Its listed script remains a proposed script.
- Completion does not establish every audit finding.
- The public record is not evidence of a DNSSEC incident.
Completion is a status, not a cryptographic verdict
IANA’s completion marker is a useful operational fact because a root-zone DNSSEC ceremony is a visible control point. Ceremony 62 is listed at the Key Management Facility West in El Segundo, with a published start of 20:00 UTC on 12 August. The same page provides a replay of the live broadcast. Those are reader-visible records of a completed procedure, not a shorthand for every conclusion someone might want to draw about the root zone.
The listed objectives matter because they are unusually specific. The page names signing ZSKs for 2026Q4 and destroying Hardware Security Modules 5W and 6W. But the page’s public description of objectives should not be turned into a per-objective audit report. It does not say which audit tests were performed, publish a comparative performance metric, or give a new resolver instruction.
Why the KSK name can mislead
The ceremony is called a Root KSK ceremony, while its displayed objectives include ZSK work and hardware retirement. That distinction is worth preserving. The public page does not say that a new KSK became the root-zone trust anchor on 12 August, and it does not announce a KSK rollover. A reader should not infer either event merely from the ceremony label or from the fact that the event has been marked complete.
IANA’s DNSSEC information page describes its role as operator of the KSK for the DNS root zone and points readers to trust anchors, rollovers, ceremony materials, policies and third-party audit certification as distinct public surfaces. In other words, the governance record is deliberately distributed: a ceremony page can establish that a particular event occurred, while different records are needed to establish a trust-anchor transition or an audit finding.
The practical watchpoint
The useful next question is documentary, not speculative. IANA already offers the replay and lists a proposed ceremony script, the signing-computer operating-system image and its published SHA-256 file. Later formal audit footage or other materials may make the public record more detailed. Until those materials say more, completion supports a narrow conclusion: the scheduled ceremony was carried out. It does not establish a security incident, a resolver-behaviour change, a root-zone alteration, or the operational result of every individual ceremony step.
