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
|
|
|
| 2 DNSKEY RR found
|
|
|
| Public Key with Algorithm 8, KeyTag 20038, Flags 256 |
|
|
| Public Key with Algorithm 8, KeyTag 20326, 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: 20.09.2024, 00:00:00 +, Signature-Inception: 30.08.2024, 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: top
|
top
| 2 DS RR in the parent zone found
|
|
|
| DS with Algorithm 8, KeyTag 56384, DigestType 2 and Digest ujeMWRNATsZU31RPUZsPsofhQNZNrF1Z40mWI5PBeUU= |
|
|
| DS with Algorithm 8, KeyTag 26780, DigestType 2 and Digest XW54ae6OO1NqYX3olILd0dy52527GsM9btNR4soJWxs= |
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
| RRSIG-Owner top., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.09.2024, 05:00:00 +, Signature-Inception: 04.09.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root) |
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20038 used to validate the DS RRSet in the parent zone
|
|
|
| 2 DNSKEY RR found
|
|
|
| Public Key with Algorithm 8, KeyTag 26780, Flags 257 (SEP = Secure Entry Point) |
|
|
| Public Key with Algorithm 8, KeyTag 62640, Flags 256 |
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
| RRSIG-Owner top., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2024, 18:59:28 +, Signature-Inception: 03.09.2024, 17:29:28 +, KeyTag 26780, Signer-Name: top |
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26780 used to validate the DNSKEY RRSet
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26780, DigestType 2 and Digest "XW54ae6OO1NqYX3olILd0dy52527GsM9btNR4soJWxs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
Zone: usp-shzlt.top
|
usp-shzlt.top
| 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 "oe88cs42ctveo5s1semhva0bmcmbfuvn" between the hashed NSEC3-owner "oe87guhhkkr9o7u7aib6u3aqli3rd46l" and the hashed NextOwner "oe88gqj8f8hto8175qep4sdr1drr7nj7". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner oe87guhhkkr9o7u7aib6u3aqli3rd46l.top., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2024, 19:59:08 +, Signature-Inception: 03.09.2024, 18:29:08 +, KeyTag 62640, Signer-Name: top |
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "i7bkfsk8a85oj5csog3mimtr7cspf7uu" as Owner. That's the Hash of "top" with the NextHashedOwnerName "i7bkmjr2kla4i922gp83otu1d7e30ega". So that domain name is the Closest Encloser of "usp-shzlt.top". Opt-Out: False.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner i7bkfsk8a85oj5csog3mimtr7cspf7uu.top., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.09.2024, 09:18:58 +, Signature-Inception: 24.08.2024, 07:48:58 +, KeyTag 62640, Signer-Name: top |
|
|
| The ClosestEncloser says, that "*.top" with the Hash "ik0v2n13a1gso00rml202aduff89o41e" 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 "ik0v05kbvhjqgjsfri3ladboc2q055uf" and the Next Owner "ik0v47539276sbqe2vhtsbkvl8jv231c", 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 ik0v05kbvhjqgjsfri3ladboc2q055uf.top., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2024, 19:59:08 +, Signature-Inception: 03.09.2024, 18:29:08 +, KeyTag 62640, Signer-Name: top |
|
Zone: www.usp-shzlt.top
|
www.usp-shzlt.top
| 0 DS RR in the parent zone found
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "i7bkfsk8a85oj5csog3mimtr7cspf7uu" as Owner. That's the Hash of "top" with the NextHashedOwnerName "i7bkmjr2kla4i922gp83otu1d7e30ega". So that domain name is the Closest Encloser of "www.usp-shzlt.top". Opt-Out: False.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner i7bkfsk8a85oj5csog3mimtr7cspf7uu.top., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.09.2024, 09:18:58 +, Signature-Inception: 24.08.2024, 07:48:58 +, KeyTag 62640, Signer-Name: top |
|
|
| The ClosestEncloser says, that "*.top" with the Hash "ik0v2n13a1gso00rml202aduff89o41e" 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 "ik0v05kbvhjqgjsfri3ladboc2q055uf" and the Next Owner "ik0v47539276sbqe2vhtsbkvl8jv231c", 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 ik0v05kbvhjqgjsfri3ladboc2q055uf.top., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2024, 19:59:08 +, Signature-Inception: 03.09.2024, 18:29:08 +, KeyTag 62640, Signer-Name: top |