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: 21.08.2024, 00:00:00 +, Signature-Inception: 31.07.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: online
|
online
| 2 DS RR in the parent zone found
|
|
|
| DS with Algorithm 8, KeyTag 4267, DigestType 2 and Digest ZtcBBgnLGema0dooM92rjKLnrMHOhwzCjSnnbrU9Obo= |
|
|
| DS with Algorithm 8, KeyTag 19282, DigestType 2 and Digest JwaiFr04Klgjx0bOaFy8hMoSqcIn5HeSq9mQ+niF27A= |
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
| RRSIG-Owner online., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.08.2024, 17:00:00 +, Signature-Inception: 06.08.2024, 16: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 19282, Flags 257 (SEP = Secure Entry Point) |
|
|
| Public Key with Algorithm 8, KeyTag 40750, Flags 256 |
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
| RRSIG-Owner online., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 30.08.2024, 17:09:44 +, Signature-Inception: 31.07.2024, 15:39:44 +, KeyTag 19282, Signer-Name: online |
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 19282 used to validate the DNSKEY RRSet
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 19282, DigestType 2 and Digest "JwaiFr04Klgjx0bOaFy8hMoSqcIn5HeSq9mQ+niF27A=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
Zone: stoff81.online
|
stoff81.online
| 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 "bjqemtbhqv2ttme27l9qr2rt58apdqa2" between the hashed NSEC3-owner "bjq1lntefck31g5701umff4bft98vjcr" and the hashed NextOwner "bjqh92i9gu5as4ejtrhk1u29j9nvihet". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner bjq1lntefck31g5701umff4bft98vjcr.online., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2024, 17:09:44 +, Signature-Inception: 31.07.2024, 15:39:44 +, KeyTag 40750, Signer-Name: online |
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "1ribnbjb5koke6vekotivtq00v2eqsdj" as Owner. That's the Hash of "online" with the NextHashedOwnerName "1riid8g9tuqkkq0g8doh8lu6fddm3pu9". So that domain name is the Closest Encloser of "stoff81.online". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1ribnbjb5koke6vekotivtq00v2eqsdj.online., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2024, 17:09:44 +, Signature-Inception: 31.07.2024, 15:39:44 +, KeyTag 40750, Signer-Name: online |
|
|
| The ClosestEncloser says, that "*.online" with the Hash "87bmdi0a1gjrjop3fv5010fhb8ondd76" 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 "87bijoaphtvh72qqvoejb6janhsel6h4" and the Next Owner "87clo070ng0hopsn534i6lc5rsijfong", 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 87bijoaphtvh72qqvoejb6janhsel6h4.online., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2024, 17:09:44 +, Signature-Inception: 31.07.2024, 15:39:44 +, KeyTag 40750, Signer-Name: online |
|
Zone: www.stoff81.online
|
www.stoff81.online
| 0 DS RR in the parent zone found
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "1ribnbjb5koke6vekotivtq00v2eqsdj" as Owner. That's the Hash of "online" with the NextHashedOwnerName "1riid8g9tuqkkq0g8doh8lu6fddm3pu9". So that domain name is the Closest Encloser of "www.stoff81.online". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1ribnbjb5koke6vekotivtq00v2eqsdj.online., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2024, 17:09:44 +, Signature-Inception: 31.07.2024, 15:39:44 +, KeyTag 40750, Signer-Name: online |
|
|
| The ClosestEncloser says, that "*.online" with the Hash "87bmdi0a1gjrjop3fv5010fhb8ondd76" 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 "87bijoaphtvh72qqvoejb6janhsel6h4" and the Next Owner "87clo070ng0hopsn534i6lc5rsijfong", 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 87bijoaphtvh72qqvoejb6janhsel6h4.online., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.08.2024, 17:09:44 +, Signature-Inception: 31.07.2024, 15:39:44 +, KeyTag 40750, Signer-Name: online |