Zone (*) | DNSSEC - Informations |
---|
|
|
Zone: (root)
|
|
(root)
| 1 DS RR published
|
|
|
|
|
| • 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 22545, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 59944, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.10.2019, 00:00:00 +, Signature-Inception: 01.10.2019, 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: cc
|
|
cc
| 2 DS RR in the parent zone found
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner cc., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.10.2019, 17:00:00 +, Signature-Inception: 10.10.2019, 16:00:00 +, KeyTag 22545, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 22545 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 519, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 31648, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 38500, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner cc., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.10.2019, 14:34:08 +, Signature-Inception: 02.10.2019, 14:29:08 +, KeyTag 519, Signer-Name: cc
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 519 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 519, DigestType 1 and Digest "coXvBeG05nnU8HLuqbAJU+AfOuI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 519, DigestType 2 and Digest "4exklavTRWLm9DPe4gHmxqUssQr2nATWddppLS1WaJc=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: helco.cc
|
|
helco.cc
| 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 "72ii6ct1mj8266u9vvfj4mvceavrla7f" between the hashed NSEC3-owner "72dv4m2l0ubg7aq30182ffjtu1gteabc" and the hashed NextOwner "73majgj3rah421ph49l7qj46t2miuef9". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 72dv4m2l0ubg7aq30182ffjtu1gteabc.cc., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.10.2019, 03:09:33 +, Signature-Inception: 11.10.2019, 03:09:33 +, KeyTag 38500, Signer-Name: cc
|
|
|
|
|
| 0 DNSKEY RR found
|
|
|
|
|
|
|
|
|
Zone: cloud.helco.cc
|
|
cloud.helco.cc
| 0 DS RR in the parent zone found
|
|
|
|
|
| 0 DNSKEY RR found
|
|
|
|
|
|
|
|
|
Zone: www.cloud.helco.cc
|
|
www.cloud.helco.cc
| 0 DS RR in the parent zone found
|