Zone (*) DNSSEC - Informations Zone : (root)(root) 1 DS RR published DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=
• Status: Valid because published2 DNSKEY RR found Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)
Public Key with Algorithm 8, KeyTag 42351, Flags 256
1 RRSIG RR to validate DNSKEY RR found RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 13.03.2021, 00:00:00 +, Signature-Inception: 20.02.2021, 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 zoneZone : cncn 1 DS RR in the parent zone found DS with Algorithm 8, KeyTag 57724, DigestType 2 and Digest XQQjYz6ySkmb54qiLRwMm6NiGP9J/ZWkzfGkrZfGcEQ=
1 RRSIG RR to validate DS RR found RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.03.2021, 05:00:00 +, Signature-Inception: 23.02.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 42351 used to validate the DS RRSet in the parent zone2 DNSKEY RR found Public Key with Algorithm 8, KeyTag 38388, Flags 256
Public Key with Algorithm 8, KeyTag 57724, Flags 257 (SEP = Secure Entry Point)
2 RRSIG RR to validate DNSKEY RR found RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.03.2021, 11:47:06 +, Signature-Inception: 12.02.2021, 10:50:03 +, KeyTag 38388, Signer-Name: cn
RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.03.2021, 11:47:06 +, Signature-Inception: 12.02.2021, 10:50:03 +, KeyTag 57724, Signer-Name: cn
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 38388 used to validate the DNSKEY RRSet• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 57724 used to validate the DNSKEY RRSet• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 57724, DigestType 2 and Digest "XQQjYz6ySkmb54qiLRwMm6NiGP9J/ZWkzfGkrZfGcEQ=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zoneZone : 8w4k.cn8w4k.cn 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 "sa9i4rb0k7ukgptk75lim4mt4kth7k59" between the hashed NSEC3-owner "sa792le0081me0rtvj551r4o4ebrtlbp" and the hashed NextOwner "sabmn2nn4icqisuauu1q52keti2lkdsf". So the parent zone confirmes the not-existence of a DS RR.Bitmap: CNAME, RRSIG Validated: RRSIG-Owner sa792le0081me0rtvj551r4o4ebrtlbp.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 14.03.2021, 10:02:54 +, Signature-Inception: 12.02.2021, 09:40:18 +, KeyTag 38388, Signer-Name: cn
DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3qdaqa092ee5belp64a74ebnb8j53d7e" as Owner. That's the Hash of "cn" with the NextHashedOwnerName "3qlmp0qrnq96g5afgopnb7u7ij4mbp4b". So that domain name is the Closest Encloser of "8w4k.cn". Opt-Out: True.Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3qdaqa092ee5belp64a74ebnb8j53d7e.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 14.03.2021, 11:02:43 +, Signature-Inception: 12.02.2021, 10:21:03 +, KeyTag 38388, Signer-Name: cn
The ClosestEncloser says, that "*.cn" with the Hash "l8hgald0tmque21ass9o122u7tpvassj" 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 "l8e8pqnl0kr4eiek7gt20h5qovd7a9ov" and the Next Owner "l8oqc8tsb8dke38diqmk2eh9j33tcn6e", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: TrueBitmap: CNAME, RRSIG Validated: RRSIG-Owner l8e8pqnl0kr4eiek7gt20h5qovd7a9ov.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 14.03.2021, 08:52:19 +, Signature-Inception: 12.02.2021, 08:44:35 +, KeyTag 38388, Signer-Name: cn
Zone : www.8w4k.cnwww.8w4k.cn 0 DS RR in the parent zone found DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3qdaqa092ee5belp64a74ebnb8j53d7e" as Owner. That's the Hash of "cn" with the NextHashedOwnerName "3qlmp0qrnq96g5afgopnb7u7ij4mbp4b". So that domain name is the Closest Encloser of "www.8w4k.cn". Opt-Out: True.Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3qdaqa092ee5belp64a74ebnb8j53d7e.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 14.03.2021, 11:02:43 +, Signature-Inception: 12.02.2021, 10:21:03 +, KeyTag 38388, Signer-Name: cn
The ClosestEncloser says, that "*.cn" with the Hash "l8hgald0tmque21ass9o122u7tpvassj" 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 "l8e8pqnl0kr4eiek7gt20h5qovd7a9ov" and the Next Owner "l8oqc8tsb8dke38diqmk2eh9j33tcn6e", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: TrueBitmap: CNAME, RRSIG Validated: RRSIG-Owner l8e8pqnl0kr4eiek7gt20h5qovd7a9ov.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 14.03.2021, 08:52:19 +, Signature-Inception: 12.02.2021, 08:44:35 +, KeyTag 38388, Signer-Name: cn