| Zone (*) | DNSSEC - Informations |
|---|
|
|
Zone: (root)
|
|
(root)
| 1 DS RR published
|
|
|
|
|
| DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=
|
|
|
|
|
| • Status: Valid because published
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 21831, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 03.03.2026, 00:00:00 +, Signature-Inception: 10.02.2026, 00:00:00 +, KeyTag 20326, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: is
|
|
is
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 13, KeyTag 46824, DigestType 2 and Digest SnzPbwDRe5GKJKEubk8RSJnkI+pKu5z3UZvoH6Im55s=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner is., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.02.2026, 21:00:00 +, Signature-Inception: 13.02.2026, 20:00:00 +, KeyTag 21831, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 21831 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 21463, Flags 256
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 46824, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner is., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.02.2026, 14:25:19 +, Signature-Inception: 09.02.2026, 12:55:19 +, KeyTag 46824, Signer-Name: is
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 46824 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 46824, DigestType 2 and Digest "SnzPbwDRe5GKJKEubk8RSJnkI+pKu5z3UZvoH6Im55s=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: molekn.is
|
|
molekn.is
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "la95f14igknh6mn5rv7uu7sgmkip9ekg" between the hashed NSEC3-owner "la929e07ts55d7gdim69mttg6g1b762b" and the hashed NextOwner "la973k635pm0ha464m2qgqgn1sra8skf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner la929e07ts55d7gdim69mttg6g1b762b.is., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 27.02.2026, 12:50:02 +, Signature-Inception: 13.02.2026, 11:20:02 +, KeyTag 21463, Signer-Name: is
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3v0mqho4oalhuhi7te0appd1fg5pnqgq" as Owner. That's the Hash of "is" with the NextHashedOwnerName "3v109jrsjv46cms4eonc3vljkb0ueflg". So that domain name is the Closest Encloser of "molekn.is". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3v0mqho4oalhuhi7te0appd1fg5pnqgq.is., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 27.02.2026, 12:50:02 +, Signature-Inception: 13.02.2026, 11:20:02 +, KeyTag 21463, Signer-Name: is
|
|
|
|
|
| The ClosestEncloser says, that "*.is" with the Hash "h0jeciovdmu313psigdbldvk06ep79ke" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "h0jbdf5p23b3lv4f4ac7p5c5rdmgdfts" and the Next Owner "h0jl2qedras1r8v7vctc8ncrdvchaetg", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: No Bitmap? Validated: RRSIG-Owner h0jbdf5p23b3lv4f4ac7p5c5rdmgdfts.is., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 27.02.2026, 12:50:02 +, Signature-Inception: 13.02.2026, 11:20:02 +, KeyTag 21463, Signer-Name: is
|
|
|
Zone: www.molekn.is
|
|
www.molekn.is
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3v0mqho4oalhuhi7te0appd1fg5pnqgq" as Owner. That's the Hash of "is" with the NextHashedOwnerName "3v109jrsjv46cms4eonc3vljkb0ueflg". So that domain name is the Closest Encloser of "www.molekn.is". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3v0mqho4oalhuhi7te0appd1fg5pnqgq.is., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 27.02.2026, 12:50:02 +, Signature-Inception: 13.02.2026, 11:20:02 +, KeyTag 21463, Signer-Name: is
|
|
|
|
|
| The ClosestEncloser says, that "*.is" with the Hash "h0jeciovdmu313psigdbldvk06ep79ke" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "h0jbdf5p23b3lv4f4ac7p5c5rdmgdfts" and the Next Owner "h0jl2qedras1r8v7vctc8ncrdvchaetg", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: No Bitmap? Validated: RRSIG-Owner h0jbdf5p23b3lv4f4ac7p5c5rdmgdfts.is., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 27.02.2026, 12:50:02 +, Signature-Inception: 13.02.2026, 11:20:02 +, KeyTag 21463, Signer-Name: is
|