Zone (*) DNSSEC - Informations (beta) Zone : (root)(root) 1 DS RR published • 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 22545, Flags 256 1 RRSIG RR to validate DNSKEY RR found • Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2019, 00:00:00, Signature-Inception: 30.11.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 zoneZone : dede 2 DS RR in the parent zone found 1 RRSIG RR to validate DS RR found Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.12.2019, 05:00:00, Signature-Inception: 01.12.2019, 04: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 zone3 DNSKEY RR found Public Key with Algorithm 8, KeyTag 18318, Flags 256 Public Key with Algorithm 8, KeyTag 26008, Flags 256 Public Key with Algorithm 8, KeyTag 45580, Flags 257 (SEP = Secure Entry Point) 1 RRSIG RR to validate DNSKEY RR found • Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 12.12.2019, 08:36:16, Signature-Inception: 28.11.2019, 07:06:16, KeyTag 45580, Signer-Name: de• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 45580 used to validate the DNSKEY RRSet• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 45580, DigestType 2 and Digest "kYwy4vEiEXZr5iJmdPRHRY8iWbmg2HtE0p1Vr+ymsuE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zoneZone : efmsn.deefmsn.de 0 DS RR in the parent zone found DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR. 0 DNSKEY RR found Zone : c.efmsn.dec.efmsn.de 0 DS RR in the parent zone found Zone : www.c.efmsn.dewww.c.efmsn.de 0 DS RR in the parent zone found Zone : (root)(root) 1 DS RR published • 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 22545, Flags 256 1 RRSIG RR to validate DNSKEY RR found • Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2019, 00:00:00, Signature-Inception: 30.11.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 zoneZone : netnet 1 DS RR in the parent zone found 1 RRSIG RR to validate DS RR found Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.12.2019, 05:00:00, Signature-Inception: 01.12.2019, 04: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 zone2 DNSKEY RR found Public Key with Algorithm 8, KeyTag 35886, Flags 257 (SEP = Secure Entry Point) Public Key with Algorithm 8, KeyTag 36407, Flags 256 1 RRSIG RR to validate DNSKEY RR found • Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.12.2019, 17:28:30, Signature-Inception: 26.11.2019, 17:23:30, KeyTag 35886, Signer-Name: net• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35886 used to validate the DNSKEY RRSet• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest "eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zoneZone : myfritz.netmyfritz.net 0 DS RR in the parent zone found DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR. 0 DNSKEY RR found Zone : bbsr5zdrx14xyry2.myfritz.netbbsr5zdrx14xyry2.myfritz.net 0 DS RR in the parent zone found 0 DNSKEY RR found Zone : nextcloud.bbsr5zdrx14xyry2.myfritz.netnextcloud.bbsr5zdrx14xyry2.myfritz.net 0 DS RR in the parent zone found 0 DNSKEY RR found