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 46780, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.11.2023, 00:00:00 +, Signature-Inception: 31.10.2023, 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: nl
|
|
nl
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 13, KeyTag 17153, DigestType 2 and Digest xd/dyR51MlYqNfPCzTCCOJS+CPIBAfGr9FyKuXOfP0k=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner nl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.11.2023, 05:00:00 +, Signature-Inception: 03.11.2023, 04:00:00 +, KeyTag 46780, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 46780 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 17153, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 52707, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner nl., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 15.11.2023, 03:24:24 +, Signature-Inception: 01.11.2023, 11:10:17 +, KeyTag 17153, Signer-Name: nl
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 17153 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 17153, DigestType 2 and Digest "xd/dyR51MlYqNfPCzTCCOJS+CPIBAfGr9FyKuXOfP0k=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: mvdnes.nl
|
|
mvdnes.nl
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 13, KeyTag 9451, DigestType 2 and Digest Lg0f4NsK8izRLD9V5dEK4vxQozYw1ugxmY2a+rfXa+w=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.11.2023, 00:43:01 +, Signature-Inception: 01.11.2023, 11:10:17 +, KeyTag 52707, Signer-Name: nl
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 52707 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 9451, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 57432, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 9451, Signer-Name: mvdnes.nl
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 9451 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 9451, DigestType 2 and Digest "Lg0f4NsK8izRLD9V5dEK4vxQozYw1ugxmY2a+rfXa+w=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 204.168.175.173
Validated: RRSIG-Owner mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 include:spf.messagingengine.com ~all
Validated: RRSIG-Owner mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 28 validates the AAAA - Result: 2001:4C3C:0700:0100:0000:0000:0010:0001
Validated: RRSIG-Owner mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 257 validates the CAA - Result: 32773|issueletsencrypt.org
Validated: RRSIG-Owner mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "gf7us8f88bejhbgh8dgoin4q10cnej7q" equal the hashed NSEC3-owner "gf7us8f88bejhbgh8dgoin4q10cnej7q" and the hashed NextOwner "ibailnnkds2k4omhmmkaccutrkt0kkod". 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, CAA Validated: RRSIG-Owner gf7us8f88bejhbgh8dgoin4q10cnej7q.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.mvdnes.nl) sends a valid NSEC3 RR as result with the hashed owner name "gf7us8f88bejhbgh8dgoin4q10cnej7q" (unhashed: mvdnes.nl). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner gf7us8f88bejhbgh8dgoin4q10cnej7q.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "l0bcte84vr4abdcplg7re0i32asu74b6" (unhashed: _tcp.mvdnes.nl) with the owner "ibailnnkds2k4omhmmkaccutrkt0kkod" and the NextOwner "plm07202p21k1r31qn0lcqb4og0d1jdk". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "ibailnnkds2k4omhmmkaccutrkt0kkod" (unhashed: *.mvdnes.nl) as the Wildcard-Expansion of the Closest Encloser of the query name "m4g8ms8m7irvs21vn0ubd28k35sp9gpe". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). TLSA-Query (_443._tcp.mvdnes.nl) sends a valid NSEC3 RR as result with the hashed query name "m4g8ms8m7irvs21vn0ubd28k35sp9gpe" between the hashed NSEC3-owner "ibailnnkds2k4omhmmkaccutrkt0kkod" and the hashed NextOwner "plm07202p21k1r31qn0lcqb4og0d1jdk". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, MX, TXT, AAAA, RRSIG, CAA Validated: RRSIG-Owner ibailnnkds2k4omhmmkaccutrkt0kkod.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.mvdnes.nl
|
|
www.mvdnes.nl
| 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 "fn6g23punvcl6f6ipluif87q5fl9ovdu" between the hashed NSEC3-owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the hashed NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "gf7us8f88bejhbgh8dgoin4q10cnej7q" as Owner. That's the Hash of "mvdnes.nl" with the NextHashedOwnerName "ibailnnkds2k4omhmmkaccutrkt0kkod". So that domain name is the Closest Encloser of "www.mvdnes.nl". Opt-Out: False.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner gf7us8f88bejhbgh8dgoin4q10cnej7q.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| The ClosestEncloser says, that "*.mvdnes.nl" with the Hash "ibailnnkds2k4omhmmkaccutrkt0kkod" 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 "gf7us8f88bejhbgh8dgoin4q10cnej7q" and the Next Owner "ibailnnkds2k4omhmmkaccutrkt0kkod", 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, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner gf7us8f88bejhbgh8dgoin4q10cnej7q.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| The ClosestEncloser says, that "*.mvdnes.nl" with the Hash "ibailnnkds2k4omhmmkaccutrkt0kkod" 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 "ibailnnkds2k4omhmmkaccutrkt0kkod" and the Next Owner "plm07202p21k1r31qn0lcqb4og0d1jdk", 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, MX, TXT, AAAA, RRSIG, CAA Validated: RRSIG-Owner ibailnnkds2k4omhmmkaccutrkt0kkod.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 204.168.175.173. 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.mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 include:spf.messagingengine.com ~all. 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.mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 60 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 28 validates the AAAA - Result: 2001:4C3C:0700:0100:0000:0000:0010: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.mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| RRSIG Type 257 validates the CAA - Result: 32773|issueletsencrypt.org. 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.mvdnes.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "gf7us8f88bejhbgh8dgoin4q10cnej7q" (unhashed: mvdnes.nl). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner gf7us8f88bejhbgh8dgoin4q10cnej7q.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "ibailnnkds2k4omhmmkaccutrkt0kkod" (unhashed: *.mvdnes.nl) as the Wildcard-Expansion of the Closest Encloser of the query name "fn6g23punvcl6f6ipluif87q5fl9ovdu". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, MX, TXT, AAAA, RRSIG, CAA Validated: RRSIG-Owner ibailnnkds2k4omhmmkaccutrkt0kkod.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.www.mvdnes.nl) sends a valid NSEC3 RR as result with the hashed owner name "gf7us8f88bejhbgh8dgoin4q10cnej7q" (unhashed: mvdnes.nl). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner gf7us8f88bejhbgh8dgoin4q10cnej7q.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "fn6g23punvcl6f6ipluif87q5fl9ovdu" (unhashed: www.mvdnes.nl) with the owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "ibailnnkds2k4omhmmkaccutrkt0kkod" (unhashed: *.mvdnes.nl) as the Wildcard-Expansion of the Closest Encloser of the query name "9f8rl38339es9bm9834j00nd6pg8kge4". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: A, MX, TXT, AAAA, RRSIG, CAA Validated: RRSIG-Owner ibailnnkds2k4omhmmkaccutrkt0kkod.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed query name "fn6g23punvcl6f6ipluif87q5fl9ovdu" between the hashed NSEC3-owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the hashed NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So the zone confirmes the not-existence of that A RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| 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 "fn6g23punvcl6f6ipluif87q5fl9ovdu" between the hashed NSEC3-owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the hashed NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| 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 "fn6g23punvcl6f6ipluif87q5fl9ovdu" between the hashed NSEC3-owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the hashed NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So the zone confirmes the not-existence of that TXT RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| 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.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "fn6g23punvcl6f6ipluif87q5fl9ovdu" between the hashed NSEC3-owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the hashed NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So the zone confirmes the not-existence of that AAAA RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| 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 "fn6g23punvcl6f6ipluif87q5fl9ovdu" between the hashed NSEC3-owner "fhm84s9kllms0rka8ko3u2m0f3v8u3a2" and the hashed NextOwner "gf7us8f88bejhbgh8dgoin4q10cnej7q". So the zone confirmes the not-existence of that CAA RR.
Bitmap: A, AAAA, RRSIG Validated: RRSIG-Owner fhm84s9kllms0rka8ko3u2m0f3v8u3a2.mvdnes.nl., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.11.2023, 00:00:00 +, Signature-Inception: 26.10.2023, 00:00:00 +, KeyTag 57432, Signer-Name: mvdnes.nl
|
|
|
|
|
| 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.
|