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
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 9799, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 14748, 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: 22.01.2022, 00:00:00 +, Signature-Inception: 01.01.2022, 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: com
|
|
com
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.01.2022, 21:00:00 +, Signature-Inception: 10.01.2022, 20:00:00 +, KeyTag 9799, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 9799 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 15549, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 38535, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.01.2022, 19:24:21 +, Signature-Inception: 05.01.2022, 19:19:21 +, KeyTag 30909, Signer-Name: com
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: techsolvency.com
|
|
techsolvency.com
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 11881, DigestType 2 and Digest x04ikgMLKPKDcmnvJrK3HsGbKK59fDan6NEelTUFTeo=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner techsolvency.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.01.2022, 05:18:49 +, Signature-Inception: 11.01.2022, 04:08:49 +, KeyTag 15549, Signer-Name: com
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 15549 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 11881, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 21283, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner techsolvency.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 11881, Signer-Name: techsolvency.com
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 11881 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 11881, DigestType 2 and Digest "x04ikgMLKPKDcmnvJrK3HsGbKK59fDan6NEelTUFTeo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 216.92.135.245
Validated: RRSIG-Owner techsolvency.com., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 a include:_spf.google.com include:spfc28.carrierzone.com -all
Validated: RRSIG-Owner techsolvency.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| RRSIG Type 257 validates the CAA - Result: 5|iodefmailto:royce@tycho.org
5|issueletsencrypt.org
Validated: RRSIG-Owner techsolvency.com., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "5d5fubur6642eth77e07j1l5ql8jd6de" equal the hashed NSEC3-owner "5d5fubur6642eth77e07j1l5ql8jd6de" and the hashed NextOwner "6rkks4m0brmqtt7i5nn7p24fajaj7953". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner 5d5fubur6642eth77e07j1l5ql8jd6de.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "5d5fubur6642eth77e07j1l5ql8jd6de" equal the hashed NSEC3-owner "5d5fubur6642eth77e07j1l5ql8jd6de" and the hashed NextOwner "6rkks4m0brmqtt7i5nn7p24fajaj7953". 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, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner 5d5fubur6642eth77e07j1l5ql8jd6de.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.techsolvency.com) sends a valid NSEC3 RR as result with the hashed owner name "5d5fubur6642eth77e07j1l5ql8jd6de" (unhashed: techsolvency.com). So that's the Closest Encloser of the query name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CAA Validated: RRSIG-Owner 5d5fubur6642eth77e07j1l5ql8jd6de.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ilf3bp5q1mc654pvuvaq09c25ttdl015" (unhashed: _tcp.techsolvency.com) with the owner "igoqa9tqtboa0paq3uef4o4oplegkmbc" and the NextOwner "io011bu5jesnf7lmcd7mgruksgkojhnf". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, TXT, RRSIG Validated: RRSIG-Owner igoqa9tqtboa0paq3uef4o4oplegkmbc.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "edii3hb1a17sc0ferll55cko3dtl27j2" (unhashed: *.techsolvency.com) as the Wildcard-Expansion of the Closest Encloser of the query name "nqct27n821362nc7660mo0isfn1hd030". 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 edii3hb1a17sc0ferll55cko3dtl27j2.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.techsolvency.com
|
|
www.techsolvency.com
| 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 "0sf7p3onh9s1o4do731dmu7vh473v5bv" between the hashed NSEC3-owner "0sf7p3onh9s1o4do731dmu7vh473v5bv" and the hashed NextOwner "1tnr454scibj6uk9if9ajucc5tt68iii". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 0sf7p3onh9s1o4do731dmu7vh473v5bv.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 216.92.135.245
Validated: RRSIG-Owner www.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "0sf7p3onh9s1o4do731dmu7vh473v5bv" equal the hashed NSEC3-owner "0sf7p3onh9s1o4do731dmu7vh473v5bv" and the hashed NextOwner "1tnr454scibj6uk9if9ajucc5tt68iii". 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 0sf7p3onh9s1o4do731dmu7vh473v5bv.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed query name "0sf7p3onh9s1o4do731dmu7vh473v5bv" equal the hashed NSEC3-owner "0sf7p3onh9s1o4do731dmu7vh473v5bv" and the hashed NextOwner "1tnr454scibj6uk9if9ajucc5tt68iii". 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 0sf7p3onh9s1o4do731dmu7vh473v5bv.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "0sf7p3onh9s1o4do731dmu7vh473v5bv" equal the hashed NSEC3-owner "0sf7p3onh9s1o4do731dmu7vh473v5bv" and the hashed NextOwner "1tnr454scibj6uk9if9ajucc5tt68iii". 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 0sf7p3onh9s1o4do731dmu7vh473v5bv.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.www.techsolvency.com) sends a valid NSEC3 RR as result with the hashed owner name "0sf7p3onh9s1o4do731dmu7vh473v5bv" (unhashed: www.techsolvency.com). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 0sf7p3onh9s1o4do731dmu7vh473v5bv.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "qv4np59usp2n42d8r5gb1lj40jvbdugu" (unhashed: _tcp.www.techsolvency.com) with the owner "jhb4c9ee878bturbgtkdbutge5kblbmk" and the NextOwner "0sf7p3onh9s1o4do731dmu7vh473v5bv". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "kchp5d0g9oomnc5pi5gol55ge1mo8csp" (unhashed: *.www.techsolvency.com) with the owner "jhb4c9ee878bturbgtkdbutge5kblbmk" and the NextOwner "0sf7p3onh9s1o4do731dmu7vh473v5bv". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.techsolvency.com) sends a valid NSEC3 RR as result with the owner name "jhb4c9ee878bturbgtkdbutge5kblbmk" greater the NextOwner-Name "0sf7p3onh9s1o4do731dmu7vh473v5bv", so the NSEC3 covers the end of the zone. The hashed query name "tt7d707iv3bttioqfam44bt4dccf1fta" comes after the hashed Owner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner jhb4c9ee878bturbgtkdbutge5kblbmk.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed query name "0sf7p3onh9s1o4do731dmu7vh473v5bv" equal the hashed NSEC3-owner "0sf7p3onh9s1o4do731dmu7vh473v5bv" and the hashed NextOwner "1tnr454scibj6uk9if9ajucc5tt68iii". 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 0sf7p3onh9s1o4do731dmu7vh473v5bv.techsolvency.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.01.2022, 00:34:26 +, Signature-Inception: 08.01.2022, 00:34:26 +, KeyTag 21283, Signer-Name: techsolvency.com
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|