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 26470, 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: 21.02.2025, 00:00:00 +, Signature-Inception: 31.01.2025, 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: guru
|
|
guru
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 35665, DigestType 2 and Digest PMXhzRSg8t7WhWweyIeFp7mzbWOBJj2r+hrBZGhIzoI=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner guru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.02.2025, 17:00:00 +, Signature-Inception: 07.02.2025, 16:00:00 +, KeyTag 26470, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26470 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 9744, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 35658, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 35665, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner guru., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 22.02.2025, 15:46:09 +, Signature-Inception: 01.02.2025, 14:46:09 +, KeyTag 35665, Signer-Name: guru
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35665 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35665, DigestType 2 and Digest "PMXhzRSg8t7WhWweyIeFp7mzbWOBJj2r+hrBZGhIzoI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: thewwwthing.guru
|
|
thewwwthing.guru
| 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 "107gtcp60r0id3rj2mbbd90m6n433grv" between the hashed NSEC3-owner "0uqgafc1co9qt91jsbugugrsntfh5pk0" and the hashed NextOwner "10vhgl6i86d1dn2alog6nefvaqdsturj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 0uqgafc1co9qt91jsbugugrsntfh5pk0.guru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.02.2025, 15:46:09 +, Signature-Inception: 01.02.2025, 14:46:09 +, KeyTag 9744, Signer-Name: guru
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "crd83rc1tpq1t7slj28fnq0vssp4e9pu" as Owner. That's the Hash of "guru" with the NextHashedOwnerName "cs1k86jr2tdvqi0k91ldbshl6vo2eek0". So that domain name is the Closest Encloser of "thewwwthing.guru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner crd83rc1tpq1t7slj28fnq0vssp4e9pu.guru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 01.03.2025, 01:29:43 +, Signature-Inception: 08.02.2025, 00:29:43 +, KeyTag 9744, Signer-Name: guru
|
|
|
|
|
| The ClosestEncloser says, that "*.guru" with the Hash "ubucu2oil6oll3jp03du7v44fhhapvju" 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 "ubpnch8puuopap851584gdfr8vnp98qh" and the Next Owner "ucb8hmglulsv1uej6c79cuhnjos6bkq9", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ubpnch8puuopap851584gdfr8vnp98qh.guru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.02.2025, 15:46:09 +, Signature-Inception: 01.02.2025, 14:46:09 +, KeyTag 9744, Signer-Name: guru
|
|
|
Zone: www.thewwwthing.guru
|
|
www.thewwwthing.guru
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "crd83rc1tpq1t7slj28fnq0vssp4e9pu" as Owner. That's the Hash of "guru" with the NextHashedOwnerName "cs1k86jr2tdvqi0k91ldbshl6vo2eek0". So that domain name is the Closest Encloser of "www.thewwwthing.guru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner crd83rc1tpq1t7slj28fnq0vssp4e9pu.guru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 01.03.2025, 01:29:43 +, Signature-Inception: 08.02.2025, 00:29:43 +, KeyTag 9744, Signer-Name: guru
|
|
|
|
|
| The ClosestEncloser says, that "*.guru" with the Hash "ubucu2oil6oll3jp03du7v44fhhapvju" 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 "ubpnch8puuopap851584gdfr8vnp98qh" and the Next Owner "ucb8hmglulsv1uej6c79cuhnjos6bkq9", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ubpnch8puuopap851584gdfr8vnp98qh.guru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.02.2025, 15:46:09 +, Signature-Inception: 01.02.2025, 14:46:09 +, KeyTag 9744, Signer-Name: guru
|