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 14631, 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.06.2021, 00:00:00 +, Signature-Inception: 21.05.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 zone
|
|
|
Zone: net
|
|
net
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2021, 05:00:00 +, Signature-Inception: 21.05.2021, 04:00:00 +, KeyTag 14631, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 14631 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 6203, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 35886, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2021, 16:28:30 +, Signature-Inception: 19.05.2021, 16: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 zone
|
|
|
Zone: double-zed.net
|
|
double-zed.net
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 7, KeyTag 61935, DigestType 2 and Digest b5qmIobBVBwUAbL5ARGIQUsxvvYFqWxYP9Gr9Pe7upU=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner double-zed.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2021, 05:28:41 +, Signature-Inception: 21.05.2021, 04:18:41 +, KeyTag 6203, Signer-Name: net
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 6203 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 7, KeyTag 47945, Flags 256
|
|
|
|
|
| Public Key with Algorithm 7, KeyTag 61935, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 2 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner double-zed.net., Algorithm: 7, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| RRSIG-Owner double-zed.net., Algorithm: 7, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 61935, Signer-Name: double-zed.net
|
|
|
|
|
| • Status: Good - Algorithmus 7 and DNSKEY with KeyTag 47945 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Good - Algorithmus 7 and DNSKEY with KeyTag 61935 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 61935, DigestType 2 and Digest "b5qmIobBVBwUAbL5ARGIQUsxvvYFqWxYP9Gr9Pe7upU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: home.double-zed.net
|
|
home.double-zed.net
| 0 DS RR in the parent zone found
|
|
|
|
|
| 0 DNSKEY RR found
|
|
|
|
|
|
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 212.239.138.36
Validated: RRSIG-Owner home.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 60 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| RRSIG Type 5 validates the TLSA - Result (_443._tcp.home.double-zed.net): home.double-zed.net. That's a CNAME answer. RRSIG Owner has 5 labels, RRSIG Labels = 3, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name.
Validated: RRSIG-Owner _443._tcp.home.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" equal the hashed NSEC3-owner "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" and the hashed NextOwner "2h5nlf77b0lhcdi9unqjpjv65h47jlai". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed query name "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" equal the hashed NSEC3-owner "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" and the hashed NextOwner "2h5nlf77b0lhcdi9unqjpjv65h47jlai". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" equal the hashed NSEC3-owner "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" and the hashed NextOwner "2h5nlf77b0lhcdi9unqjpjv65h47jlai". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.home.double-zed.net) sends a valid NSEC3 RR as result with the hashed owner name "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" (unhashed: home.double-zed.net). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "u251t8bt0ggu93ekrlhqnptafftv9pj3" (unhashed: _tcp.home.double-zed.net) with the owner "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" and the NextOwner "2h5nlf77b0lhcdi9unqjpjv65h47jlai". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed query name "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" equal the hashed NSEC3-owner "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" and the hashed NextOwner "2h5nlf77b0lhcdi9unqjpjv65h47jlai". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.home.double-zed.net
|
|
www.home.double-zed.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 query name "n6pc90vak62itqrna2dut0hsonevda58" between the hashed NSEC3-owner "jdv65oda2td4se9drme4314ngcra0950" and the hashed NextOwner "rdass1jkjm42c6bd69fu7m9oumqggb5l". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner jdv65oda2td4se9drme4314ngcra0950.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" as Owner. That's the Hash of "home.double-zed.net" with the NextHashedOwnerName "2h5nlf77b0lhcdi9unqjpjv65h47jlai". So that domain name is the Closest Encloser of "www.home.double-zed.net". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| The ClosestEncloser says, that "*.home.double-zed.net" with the Hash "2h5nlf77b0lhcdi9unqjpjv65h47jlai" 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 "tco7eg8q5sblk89g1e5gu1eu6gimp2p4" and the Next Owner "2h5nlf77b0lhcdi9unqjpjv65h47jlai", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner tco7eg8q5sblk89g1e5gu1eu6gimp2p4.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| RRSIG Type 5 validates the CNAME - Result: home.double-zed.net. RRSIG Owner has 4 labels, RRSIG Labels = 3, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name.
Validated: RRSIG-Owner www.home.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "n6pc90vak62itqrna2dut0hsonevda58" between the hashed NSEC3-owner "jdv65oda2td4se9drme4314ngcra0950" and the hashed NextOwner "rdass1jkjm42c6bd69fu7m9oumqggb5l". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner jdv65oda2td4se9drme4314ngcra0950.double-zed.net., Algorithm: 7, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.06.2021, 19:05:22 +, Signature-Inception: 19.05.2021, 19:05:22 +, KeyTag 47945, Signer-Name: double-zed.net
|
|
|
|
|
| Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: Validated Data sent, but the NSEC3Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.
|