No significant activity was recorded during the reported window.
Keys observed: 3
Events recorded: 3
State changes (state_file): 0
State changes (rndc dnssec -status): 0
DNS observations (zone + parent): 0
iodyn-dnssec actions: 0
Key inventory
Tag
Role
Algorithm
Key id
First seen
45366
KSK
13
Ktest2.test.+013+45366
2026-04-11T11:03:18Z
7693
ZSK
13
Ktest2.test.+013+07693
2026-04-11T11:03:18Z
15503
ZSK
13
Ktest2.test.+013+15503
2026-04-11T11:03:18Z
Rollover view
Every observed key on a time axis, grouped by
(role, algorithm), with phase-coloured bars
(pre-publication / published / active / retired / removed). A
thin DS overlay stripe above each KSK row shows when the
parent-side chain of trust was actually complete, which is
often when the interesting DNSSEC stories happen. If two
algorithms are simultaneously active, the overlap region is
highlighted behind their bars.
Calendar view
Monthly calendars covering the reported window. Each day is
shaded by the number of events observed and carries a coloured
dot for every event source that fired that day. Hover any day
for the count and a sample of the events (live UI only).
Events observed via live DNS queries and reported by
rndc dnssec -status. Dots are coloured by
source, stacked to avoid overlap, and the significant
transitions are labelled inline.
File event timeline
Changes observed directly on disk — every modification to a
K*.state or K*.key file. Paired with
the DNS timeline above, divergence between the two channels is
usually where the interesting DNSSEC bugs live.
State machine timeline
Colour bars show each key's state-machine value over the window.
Separate lanes for GoalState, DNSKEYState,
KRRSIGState, ZRRSIGState, and
DSState. The rndc view is drawn below from
rndc dnssec -status; discrepancies between the two
are where bugs and BIND quirks usually live.
BIND's view (rndc dnssec -status)
Chronological event log
2026-04-11
Time
Source
Key
Type
Summary
11:03:18Z
key
ZSK 15503
key_file_observed
new K*.key for test2.test ZSK tag=15503
11:03:18Z
key
KSK 45366
key_file_observed
new K*.key for test2.test KSK tag=45366
11:03:18Z
key
ZSK 7693
key_file_observed
new K*.key for test2.test ZSK tag=7693
Per-key breakdown
For every observed key: the current K*.key timings
and K*.state fields captured at report time, plus a
calendar and split DNS / File timelines limited to that key's
events. KSKs naturally show their DS lifecycle at the parent
because DS events are tagged by key tag at emit time.
KSK · tag 45366
Algorithm: 13 ·
Key id: Ktest2.test.+013+45366 ·
First seen: 2026-04-11T11:03:18Z