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 20038, 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: 01.08.2024, 00:00:00 +, Signature-Inception: 11.07.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: tel
|
|
tel
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 31166, DigestType 2 and Digest HXtqraGgNRAHf3iadRhMphpv4xdqJj0b5SvOiTVcqo0=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner tel., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.07.2024, 18:00:00 +, Signature-Inception: 16.07.2024, 17:00:00 +, KeyTag 20038, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20038 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 29848, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 31166, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner tel., Algorithm: 8, 1 Labels, original TTL: 43200 sec, Signature-expiration: 26.07.2024, 21:32:04 +, Signature-Inception: 12.07.2024, 21:32:04 +, KeyTag 31166, Signer-Name: tel
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 31166 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 31166, DigestType 2 and Digest "HXtqraGgNRAHf3iadRhMphpv4xdqJj0b5SvOiTVcqo0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: loki.tel
|
|
loki.tel
| 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 "jusvr79u8vk4kij705ocptko0d7por7m" between the hashed NSEC3-owner "jusvr79u8vk4kij705ocptko0d7por7m" and the hashed NextOwner "jutp4eik4o73ca28h6q8cc50hcv1n2ti". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner jusvr79u8vk4kij705ocptko0d7por7m.tel., Algorithm: 8, 2 Labels, original TTL: 43200 sec, Signature-expiration: 25.07.2024, 21:29:21 +, Signature-Inception: 11.07.2024, 21:29:21 +, KeyTag 29848, Signer-Name: tel
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 48868, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 62900, Flags 256
|
|
|
|
|
| 2 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 48868, Signer-Name: loki.tel
|
|
|
|
|
| RRSIG-Owner loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 48868 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 62900 used to validate the DNSKEY RRSet
|
|
|
|
|
| Error: DNSKEY 48868 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.
|
|
|
|
|
| Error: DNSKEY 62900 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 89.58.18.247
Validated: RRSIG-Owner loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 mx -all
Validated: RRSIG-Owner loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| RRSIG Type 28 validates the AAAA - Result: 2A0A:4CC0:0000:0DC7:0000:0000:0000:1984
Validated: RRSIG-Owner loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| RRSIG Type 257 validates the CAA - Result: 5|issueletsencrypt.org
Validated: RRSIG-Owner loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "4men3qfijhc2j1u6tau501etohe0n79j" equal the hashed NSEC3-owner "4men3qfijhc2j1u6tau501etohe0n79j" and the hashed NextOwner "4mvpvg92i8b9fuuo3c8lvcrj726kau9f". 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 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.loki.tel) sends a valid NSEC3 RR as result with the hashed owner name "4men3qfijhc2j1u6tau501etohe0n79j" (unhashed: loki.tel). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "1joifhs6fl597i3hmt5jnrjtkmjhf27i" (unhashed: _tcp.loki.tel) with the owner "1esvirv9nososs3nvnfs3skufakdv5qq" and the NextOwner "248bl7cs2muta1fac199bpktmt716sna". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, SSHFP, RRSIG Validated: RRSIG-Owner 1esvirv9nososs3nvnfs3skufakdv5qq.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "vsj3m2b8et6v8eij121f7e9lk0snhg6s" (unhashed: *.loki.tel) as the Wildcard-Expansion of the Closest Encloser of the query name "dqusqof98vvfp9jqua1knl7tcidvcfpk". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.loki.tel
|
|
www.loki.tel
| 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 "bs16t4o19nmt1k9s56alg3vcdl6put7s" between the hashed NSEC3-owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the hashed NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "4men3qfijhc2j1u6tau501etohe0n79j" as Owner. That's the Hash of "loki.tel" with the NextHashedOwnerName "4mvpvg92i8b9fuuo3c8lvcrj726kau9f". So that domain name is the Closest Encloser of "www.loki.tel". Opt-Out: False.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| The ClosestEncloser says, that "*.loki.tel" with the Hash "vsj3m2b8et6v8eij121f7e9lk0snhg6s" 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 "vsj3m2b8et6v8eij121f7e9lk0snhg6s" and the Next Owner "02bt2hj8rvpp78m1dmg6vpbvaou0r9o3", 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: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| RRSIG Type 257 validates the CAA - Result: 9|issuewildletsencrypt.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.loki.tel., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed owner name "4men3qfijhc2j1u6tau501etohe0n79j" (unhashed: loki.tel). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed owner name "vsj3m2b8et6v8eij121f7e9lk0snhg6s" (unhashed: *.loki.tel) as the Wildcard-Expansion of the Closest Encloser of the query name "bs16t4o19nmt1k9s56alg3vcdl6put7s". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "4men3qfijhc2j1u6tau501etohe0n79j" (unhashed: loki.tel). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "vsj3m2b8et6v8eij121f7e9lk0snhg6s" (unhashed: *.loki.tel) as the Wildcard-Expansion of the Closest Encloser of the query name "bs16t4o19nmt1k9s56alg3vcdl6put7s". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "4men3qfijhc2j1u6tau501etohe0n79j" (unhashed: loki.tel). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "vsj3m2b8et6v8eij121f7e9lk0snhg6s" (unhashed: *.loki.tel) as the Wildcard-Expansion of the Closest Encloser of the query name "bs16t4o19nmt1k9s56alg3vcdl6put7s". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "4men3qfijhc2j1u6tau501etohe0n79j" (unhashed: loki.tel). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "vsj3m2b8et6v8eij121f7e9lk0snhg6s" (unhashed: *.loki.tel) as the Wildcard-Expansion of the Closest Encloser of the query name "bs16t4o19nmt1k9s56alg3vcdl6put7s". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.www.loki.tel) sends a valid NSEC3 RR as result with the hashed owner name "4men3qfijhc2j1u6tau501etohe0n79j" (unhashed: loki.tel). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CAA Validated: RRSIG-Owner 4men3qfijhc2j1u6tau501etohe0n79j.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "bs16t4o19nmt1k9s56alg3vcdl6put7s" (unhashed: www.loki.tel) with the owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "vsj3m2b8et6v8eij121f7e9lk0snhg6s" (unhashed: *.loki.tel) as the Wildcard-Expansion of the Closest Encloser of the query name "5nhbuk4gfsvseeqsue7lu2aqtfelllme". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: RRSIG, CAA Validated: RRSIG-Owner vsj3m2b8et6v8eij121f7e9lk0snhg6s.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed query name "bs16t4o19nmt1k9s56alg3vcdl6put7s" between the hashed NSEC3-owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the hashed NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So the zone confirmes the not-existence of that A RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| 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.
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "bs16t4o19nmt1k9s56alg3vcdl6put7s" between the hashed NSEC3-owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the hashed NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| 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 "bs16t4o19nmt1k9s56alg3vcdl6put7s" between the hashed NSEC3-owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the hashed NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So the zone confirmes the not-existence of that TXT RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| 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 "bs16t4o19nmt1k9s56alg3vcdl6put7s" between the hashed NSEC3-owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the hashed NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So the zone confirmes the not-existence of that AAAA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| 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.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed query name "bs16t4o19nmt1k9s56alg3vcdl6put7s" between the hashed NSEC3-owner "9vqht005gc0pagq26n9f54gjm0jdc0sv" and the hashed NextOwner "c8ct2i710q0172c6ufvgp5i7ufhfo8c9". So the zone confirmes the not-existence of that CAA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9vqht005gc0pagq26n9f54gjm0jdc0sv.loki.tel., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 14.08.2024, 20:01:17 +, Signature-Inception: 15.07.2024, 20:01:17 +, KeyTag 62900, Signer-Name: loki.tel
|
|
|
|
|
| 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.
|