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 20326, Flags 257 (SEP = Secure Entry Point) |
|
|
| Public Key with Algorithm 8, KeyTag 30903, Flags 256 |
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.03.2024, 00:00:00 +, Signature-Inception: 10.02.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: click
|
click
| 1 DS RR in the parent zone found
|
|
|
| DS with Algorithm 13, KeyTag 65517, DigestType 2 and Digest 0JosFMQ4JjTtzPljT7MukVEeHmQvPDhGi6JAfx0brSQ= |
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
| RRSIG-Owner click., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.02.2024, 05:00:00 +, Signature-Inception: 12.02.2024, 04:00:00 +, KeyTag 30903, Signer-Name: (root) |
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30903 used to validate the DS RRSet in the parent zone
|
|
|
| 2 DNSKEY RR found
|
|
|
| Public Key with Algorithm 13, KeyTag 29054, Flags 256 |
|
|
| Public Key with Algorithm 13, KeyTag 65517, Flags 257 (SEP = Secure Entry Point) |
|
|
| 2 RRSIG RR to validate DNSKEY RR found
|
|
|
| RRSIG-Owner click., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 13.03.2024, 08:00:48 +, Signature-Inception: 12.02.2024, 08:00:48 +, KeyTag 29054, Signer-Name: click |
|
|
| RRSIG-Owner click., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 13.03.2024, 08:00:48 +, Signature-Inception: 12.02.2024, 08:00:48 +, KeyTag 65517, Signer-Name: click |
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 29054 used to validate the DNSKEY RRSet
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 65517 used to validate the DNSKEY RRSet
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 65517, DigestType 2 and Digest "0JosFMQ4JjTtzPljT7MukVEeHmQvPDhGi6JAfx0brSQ=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
Zone: ledermann.click
|
ledermann.click
| 1 DS RR in the parent zone found
|
|
|
| DS with Algorithm 13, KeyTag 8826, DigestType 2 and Digest hnf+fhfuIt0hZliTnDoBFSj2jGxYQ79Ulv7zxVsxPkw= |
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
| RRSIG-Owner ledermann.click., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 13.03.2024, 08:00:48 +, Signature-Inception: 12.02.2024, 08:00:48 +, KeyTag 29054, Signer-Name: click |
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 29054 used to validate the DS RRSet in the parent zone
|
|
|
| 1 DNSKEY RR found
|
|
|
| Public Key with Algorithm 13, KeyTag 8826, Flags 256 |
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
| RRSIG-Owner ledermann.click., Algorithm: 13, 2 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 8826 used to validate the DNSKEY RRSet
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 8826, DigestType 2 and Digest "hnf+fhfuIt0hZliTnDoBFSj2jGxYQ79Ulv7zxVsxPkw=" validates local Key with the same values
|
|
|
| RRSIG Type 1 validates the A - Result: 78.47.10.194
Validated: RRSIG-Owner ledermann.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 include:_mailcust.gandi.net ?all
Validated: RRSIG-Owner ledermann.click., Algorithm: 13, 2 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| RRSIG Type 28 validates the AAAA - Result: 2A01:04F8:1C1B:5526:0000:0000:0000:0001
Validated: RRSIG-Owner ledermann.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| RRSIG Type 257 validates the CAA - Result: 5|issueletsencrypt.org
9|issuewildletsencrypt.org
Validated: RRSIG-Owner ledermann.click., Algorithm: 13, 2 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "ldmh08q020uaivhsdomf2r0vkfk33ftk" equal the hashed NSEC3-owner "ldmh08q020uaivhsdomf2r0vkfk33ftk" and the hashed NextOwner "ldmh08q020uaivhsdomf2r0vkfk33ftl". 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, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ldmh08q020uaivhsdomf2r0vkfk33ftk.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| TLSA-Query (_443._tcp.ledermann.click) sends a valid NSEC3 RR as result with the hashed owner name "6lk0e54sg8n2a0hv0k5o3d7s20bssssr" (unhashed: _tcp.ledermann.click). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner 6lk0e54sg8n2a0hv0k5o3d7s20bssssr.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "ejmld1r6391uj9mlhqhgta1g6fog81c3" (unhashed: *._tcp.ledermann.click) with the owner "ejmld1r6391uj9mlhqhgta1g6fog81c2" and the NextOwner "ejmld1r6391uj9mlhqhgta1g6fog81c4". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: No Bitmap? Validated: RRSIG-Owner ejmld1r6391uj9mlhqhgta1g6fog81c2.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
|
| TLSA-Query (_443._tcp.ledermann.click) sends a valid NSEC3 RR as result with the hashed query name "n8hjm22ffb4ufffc914jtrsjhsh7oon1" between the hashed NSEC3-owner "n8hjm22ffb4ufffc914jtrsjhsh7oon0" and the hashed NextOwner "n8hjm22ffb4ufffc914jtrsjhsh7oon2". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner n8hjm22ffb4ufffc914jtrsjhsh7oon0.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
Zone: www.ledermann.click
|
www.ledermann.click
| 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 "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" between the hashed NSEC3-owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the hashed NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ldmh08q020uaivhsdomf2r0vkfk33ftk" as Owner. That's the Hash of "ledermann.click" with the NextHashedOwnerName "ldmh08q020uaivhsdomf2r0vkfk33ftl". So that domain name is the Closest Encloser of "www.ledermann.click". Opt-Out: False.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ldmh08q020uaivhsdomf2r0vkfk33ftk.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| The ClosestEncloser says, that "*.ledermann.click" with the Hash "ug0fvkk92nhnvr5pjkt0valiiicqt6gc" 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 "ug0fvkk92nhnvr5pjkt0valiiicqt6gc" and the Next Owner "ug0fvkk92nhnvr5pjkt0valiiicqt6gd", 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, AAAA, RRSIG Validated: RRSIG-Owner ug0fvkk92nhnvr5pjkt0valiiicqt6gc.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| RRSIG Type 1 validates the A - Result: 78.47.10.194. RRSIG Owner has 3 labels, RRSIG Labels = 2, 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.ledermann.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| RRSIG Type 28 validates the AAAA - Result: 2A01:04F8:1C1B:5526:0000:0000:0000:0001. RRSIG Owner has 3 labels, RRSIG Labels = 2, 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.ledermann.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "ldmh08q020uaivhsdomf2r0vkfk33ftk" (unhashed: ledermann.click). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ldmh08q020uaivhsdomf2r0vkfk33ftk.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "ug0fvkk92nhnvr5pjkt0valiiicqt6gc" (unhashed: *.ledermann.click) as the Wildcard-Expansion of the Closest Encloser of the query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner ug0fvkk92nhnvr5pjkt0valiiicqt6gc.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "ldmh08q020uaivhsdomf2r0vkfk33ftk" (unhashed: ledermann.click). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ldmh08q020uaivhsdomf2r0vkfk33ftk.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "ug0fvkk92nhnvr5pjkt0valiiicqt6gc" (unhashed: *.ledermann.click) as the Wildcard-Expansion of the Closest Encloser of the query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner ug0fvkk92nhnvr5pjkt0valiiicqt6gc.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| TLSA-Query (_443._tcp.www.ledermann.click) sends a valid NSEC3 RR as result with the hashed owner name "ldmh08q020uaivhsdomf2r0vkfk33ftk" (unhashed: ledermann.click). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ldmh08q020uaivhsdomf2r0vkfk33ftk.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" (unhashed: www.ledermann.click) with the owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "ug0fvkk92nhnvr5pjkt0valiiicqt6gc" (unhashed: *.ledermann.click) as the Wildcard-Expansion of the Closest Encloser of the query name "bvdme32meoe2156tbf49c497n6q3j5dk". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner ug0fvkk92nhnvr5pjkt0valiiicqt6gc.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "ldmh08q020uaivhsdomf2r0vkfk33ftk" (unhashed: ledermann.click). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ldmh08q020uaivhsdomf2r0vkfk33ftk.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "ug0fvkk92nhnvr5pjkt0valiiicqt6gc" (unhashed: *.ledermann.click) as the Wildcard-Expansion of the Closest Encloser of the query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner ug0fvkk92nhnvr5pjkt0valiiicqt6gc.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" between the hashed NSEC3-owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the hashed NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So the zone confirmes the not-existence of that A RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| 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.
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" between the hashed NSEC3-owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the hashed NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| 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: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate 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.
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" between the hashed NSEC3-owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the hashed NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So the zone confirmes the not-existence of that TXT RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| 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: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate 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.
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" between the hashed NSEC3-owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the hashed NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So the zone confirmes the not-existence of that AAAA RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| 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.
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed query name "2ff2qq7eikh3lrs9fofsvk4k6rja3tl0" between the hashed NSEC3-owner "2ff2qq7eikh3lrs9fofsvk4k6rja3tkv" and the hashed NextOwner "2ff2qq7eikh3lrs9fofsvk4k6rja3tl1". So the zone confirmes the not-existence of that CAA RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 2ff2qq7eikh3lrs9fofsvk4k6rja3tkv.ledermann.click., Algorithm: 13, 3 Labels, original TTL: 10800 sec, Signature-expiration: 22.02.2024, 00:00:00 +, Signature-Inception: 01.02.2024, 00:00:00 +, KeyTag 8826, Signer-Name: ledermann.click |
|
|
| 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: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate 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.
|