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 9799, 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: 11.02.2022, 00:00:00 +, Signature-Inception: 21.01.2022, 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 : tradetrade 1 DS RR in the parent zone found DS with Algorithm 8, KeyTag 17452, DigestType 2 and Digest vMG9veMhg4TSK8sW2ayywn9/glddbzL/JIBAZ1Z6Cas=
1 RRSIG RR to validate DS RR found RRSIG-Owner trade., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.02.2022, 05:00:00 +, Signature-Inception: 29.01.2022, 04:00:00 +, KeyTag 9799, Signer-Name: (root)
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 9799 used to validate the DS RRSet in the parent zone2 DNSKEY RR found Public Key with Algorithm 8, KeyTag 11625, Flags 256
Public Key with Algorithm 8, KeyTag 17452, Flags 257 (SEP = Secure Entry Point)
2 RRSIG RR to validate DNSKEY RR found RRSIG-Owner trade., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 23.02.2022, 13:14:07 +, Signature-Inception: 24.01.2022, 12:56:14 +, KeyTag 11625, Signer-Name: trade
RRSIG-Owner trade., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 23.02.2022, 13:14:07 +, Signature-Inception: 24.01.2022, 12:56:14 +, KeyTag 17452, Signer-Name: trade
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 11625 used to validate the DNSKEY RRSet• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 17452 used to validate the DNSKEY RRSet• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 17452, DigestType 2 and Digest "vMG9veMhg4TSK8sW2ayywn9/glddbzL/JIBAZ1Z6Cas=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zoneZone : gauderskins.tradegauderskins.trade 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 "vf0qau7car9mgeafcou6ng57ah0ge6tn" between the hashed NSEC3-owner "vent9ad79rsco1ocp7uq5d2qpq24lhl5" and the hashed NextOwner "vgcnat2ai2feod36uls90tnu302s7g25". So the parent zone confirmes the not-existence of a DS RR.Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vent9ad79rsco1ocp7uq5d2qpq24lhl5.trade., Algorithm: 8, 2 Labels, original TTL: 60 sec, Signature-expiration: 28.02.2022, 11:49:43 +, Signature-Inception: 29.01.2022, 11:01:18 +, KeyTag 11625, Signer-Name: trade
DS-Query in the parent zone sends valid NSEC3 RR with the Hash "08q3dsrt308dkfr237qdbuken47oeiqo" as Owner. That's the Hash of "trade" with the NextHashedOwnerName "097kil752a9m4inomn91g6bqh9e66sad". So that domain name is the Closest Encloser of "gauderskins.trade". Opt-Out: True.Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 08q3dsrt308dkfr237qdbuken47oeiqo.trade., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 23.02.2022, 21:25:36 +, Signature-Inception: 24.01.2022, 20:59:08 +, KeyTag 11625, Signer-Name: trade
The ClosestEncloser says, that "*.trade" with the Hash "gv9ffprksuup6tao5mpkhnnsd4s02lad" 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 "gtc32eppl3b0dl1d015o1nc9d4ts14eh" and the Next Owner "h0g4pmvfgn24ccbbrrlsg0vr74re03gh", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: TrueBitmap: NS, DS, RRSIG Validated: RRSIG-Owner gtc32eppl3b0dl1d015o1nc9d4ts14eh.trade., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 25.02.2022, 14:59:37 +, Signature-Inception: 26.01.2022, 14:43:37 +, KeyTag 11625, Signer-Name: trade
Zone : www.gauderskins.tradewww.gauderskins.trade 0 DS RR in the parent zone found DS-Query in the parent zone sends valid NSEC3 RR with the Hash "08q3dsrt308dkfr237qdbuken47oeiqo" as Owner. That's the Hash of "trade" with the NextHashedOwnerName "097kil752a9m4inomn91g6bqh9e66sad". So that domain name is the Closest Encloser of "www.gauderskins.trade". Opt-Out: True.Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 08q3dsrt308dkfr237qdbuken47oeiqo.trade., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 23.02.2022, 21:25:36 +, Signature-Inception: 24.01.2022, 20:59:08 +, KeyTag 11625, Signer-Name: trade
The ClosestEncloser says, that "*.trade" with the Hash "gv9ffprksuup6tao5mpkhnnsd4s02lad" 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 "gtc32eppl3b0dl1d015o1nc9d4ts14eh" and the Next Owner "h0g4pmvfgn24ccbbrrlsg0vr74re03gh", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: TrueBitmap: NS, DS, RRSIG Validated: RRSIG-Owner gtc32eppl3b0dl1d015o1nc9d4ts14eh.trade., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 25.02.2022, 14:59:37 +, Signature-Inception: 26.01.2022, 14:43:37 +, KeyTag 11625, Signer-Name: trade