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: 01.07.2021, 00:00:00 +, Signature-Inception: 10.06.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: is
|
|
is
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 26726, DigestType 2 and Digest aYT+9WnP2yzgCvxitXY61QMG6w1IFqfGz5Ib9msSJFo=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner is., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.06.2021, 05:00:00 +, Signature-Inception: 14.06.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 26726, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 30303, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner is., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.07.2021, 15:15:35 +, Signature-Inception: 13.06.2021, 16:59:34 +, KeyTag 26726, Signer-Name: is
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26726 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26726, DigestType 2 and Digest "aYT+9WnP2yzgCvxitXY61QMG6w1IFqfGz5Ib9msSJFo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: meh.is
|
|
meh.is
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 157, DigestType 2 and Digest /jh1N8XzKQkhEY3hl9EMSyC9j8V9K2RiHZq5SfBmVNE=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner meh.is., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.06.2021, 17:13:44 +, Signature-Inception: 08.06.2021, 21:30:04 +, KeyTag 30303, Signer-Name: is
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30303 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 157, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 28824, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 57039, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner meh.is., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 157, Signer-Name: meh.is
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 157 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 157, DigestType 2 and Digest "/jh1N8XzKQkhEY3hl9EMSyC9j8V9K2RiHZq5SfBmVNE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 199.247.25.120
Validated: RRSIG-Owner meh.is., Algorithm: 8, 2 Labels, original TTL: 604800 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 include:_spf.google.com -all
have-i-been-pwned-verification=2eafe9ca075a290d7479bd53269f954e
google-site-verification=6UU8ajBLTpi9lLAL-tImm9Zf-22M6aZNU2IKjD1DZKs
Validated: RRSIG-Owner meh.is., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| RRSIG Type 28 validates the AAAA - Result: 2001:19F0:5001:111E:1A5F:3566:9305:DF1B
Validated: RRSIG-Owner meh.is., Algorithm: 8, 2 Labels, original TTL: 604800 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| RRSIG Type 257 validates the CAA - Result: 32773|iodefmailto:caa+meh.is@meh.is
32773|issueletsencrypt.org
32777|issuewildletsencrypt.org
Validated: RRSIG-Owner meh.is., Algorithm: 8, 2 Labels, original TTL: 604800 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" equal the hashed NSEC3-owner "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" and the hashed NextOwner "v3jdn6r5cc9bv1316f091bjlfes80ppk". 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.meh.is) sends a valid NSEC3 RR as result with the hashed owner name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" (unhashed: meh.is). 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "6q8hivcbci79htr585ki22gb3kf2epg8" (unhashed: _tcp.meh.is) with the owner "68jn4pqm1qucbp3qdlanuepi577utlub" and the NextOwner "7h4s2beii06adnvrklkeabcsacstifdk". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 68jn4pqm1qucbp3qdlanuepi577utlub.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "4br97qkb3ls5ther2cuqeb4jdiafn8bt" (unhashed: *.meh.is) as the Wildcard-Expansion of the Closest Encloser of the query name "iosk6bjc9b22vc8v0rp2g8pcm7vcnvir". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.meh.is
|
|
www.meh.is
| 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 "edcevt63jvetuanr991invidbum6bjk7" between the hashed NSEC3-owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the hashed NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" as Owner. That's the Hash of "meh.is" with the NextHashedOwnerName "v3jdn6r5cc9bv1316f091bjlfes80ppk". So that domain name is the Closest Encloser of "www.meh.is". Opt-Out: False.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| The ClosestEncloser says, that "*.meh.is" with the Hash "4br97qkb3ls5ther2cuqeb4jdiafn8bt" 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 "4br97qkb3ls5ther2cuqeb4jdiafn8bt" and the Next Owner "53kuob4sgd57kltc4a239b5torpnva32", 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: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 -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.meh.is., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed owner name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" (unhashed: meh.is). 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed owner name "4br97qkb3ls5ther2cuqeb4jdiafn8bt" (unhashed: *.meh.is) as the Wildcard-Expansion of the Closest Encloser of the query name "edcevt63jvetuanr991invidbum6bjk7". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" (unhashed: meh.is). 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "4br97qkb3ls5ther2cuqeb4jdiafn8bt" (unhashed: *.meh.is) as the Wildcard-Expansion of the Closest Encloser of the query name "edcevt63jvetuanr991invidbum6bjk7". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" (unhashed: meh.is). 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "4br97qkb3ls5ther2cuqeb4jdiafn8bt" (unhashed: *.meh.is) as the Wildcard-Expansion of the Closest Encloser of the query name "edcevt63jvetuanr991invidbum6bjk7". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.www.meh.is) sends a valid NSEC3 RR as result with the hashed owner name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" (unhashed: meh.is). 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "edcevt63jvetuanr991invidbum6bjk7" (unhashed: www.meh.is) with the owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "4br97qkb3ls5ther2cuqeb4jdiafn8bt" (unhashed: *.meh.is) as the Wildcard-Expansion of the Closest Encloser of the query name "kfltjvib5d19sj1ausuf31r416j2u041". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "ssspuk3o6umfbbkmdi6g9grrpio7oj7k" (unhashed: meh.is). 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 ssspuk3o6umfbbkmdi6g9grrpio7oj7k.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "4br97qkb3ls5ther2cuqeb4jdiafn8bt" (unhashed: *.meh.is) as the Wildcard-Expansion of the Closest Encloser of the query name "edcevt63jvetuanr991invidbum6bjk7". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain).
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 4br97qkb3ls5ther2cuqeb4jdiafn8bt.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| A-Query sends a valid NSEC3 RR as result with the hashed query name "edcevt63jvetuanr991invidbum6bjk7" between the hashed NSEC3-owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the hashed NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So the zone confirmes the not-existence of that A RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| 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 "edcevt63jvetuanr991invidbum6bjk7" between the hashed NSEC3-owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the hashed NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| 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 "edcevt63jvetuanr991invidbum6bjk7" between the hashed NSEC3-owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the hashed NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So the zone confirmes the not-existence of that TXT RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| 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 "edcevt63jvetuanr991invidbum6bjk7" between the hashed NSEC3-owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the hashed NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So the zone confirmes the not-existence of that AAAA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| 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 "edcevt63jvetuanr991invidbum6bjk7" between the hashed NSEC3-owner "e7vsgdf8vfceijrql13sq0k2s9951j9a" and the hashed NextOwner "fm4tv23s3d11cncfal3pqgh56hrug28q". So the zone confirmes the not-existence of that CAA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner e7vsgdf8vfceijrql13sq0k2s9951j9a.meh.is., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 02.07.2021, 22:24:33 +, Signature-Inception: 10.06.2021, 22:24:33 +, KeyTag 28824, Signer-Name: meh.is
|
|
|
|
|
| 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.
|