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 42351, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 03.03.2021, 00:00:00 +, Signature-Inception: 10.02.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: pl
|
|
pl
| 2 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 6064, DigestType 2 and Digest LNfT0WTYI51OqJkaYslmelrhn7+96+s1y4JdH2aI7qY=
|
|
|
|
|
| DS with Algorithm 8, KeyTag 51352, DigestType 2 and Digest xCgpGN5hap47/+wfBlKkHPc9t+9/V4Xbc1np5Z1ABIw=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.02.2021, 05:00:00 +, Signature-Inception: 15.02.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 42351 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 6064, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 51352, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 54375, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.03.2021, 12:00:00 +, Signature-Inception: 14.02.2021, 12:00:00 +, KeyTag 51352, Signer-Name: pl
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 51352 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 51352, DigestType 2 and Digest "xCgpGN5hap47/+wfBlKkHPc9t+9/V4Xbc1np5Z1ABIw=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: com.pl
|
|
com.pl
| 2 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 59401, DigestType 2 and Digest 4SFeA4s38tgRXhvXX/fhKKtiYBrs4O+ucDVdQP2K9Ig=
|
|
|
|
|
| DS with Algorithm 8, KeyTag 46435, DigestType 2 and Digest OzCqxkWFMfp0O2kYKvBhAUDx3acOu3LXh/Pr/86EnDM=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner com.pl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.03.2021, 12:00:00 +, Signature-Inception: 14.02.2021, 12:00:00 +, KeyTag 54375, Signer-Name: pl
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 54375 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 28974, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 46435, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 59401, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner com.pl., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.03.2021, 12:00:00 +, Signature-Inception: 14.02.2021, 12:00:00 +, KeyTag 46435, Signer-Name: com.pl
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 46435 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 46435, DigestType 2 and Digest "OzCqxkWFMfp0O2kYKvBhAUDx3acOu3LXh/Pr/86EnDM=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: trisoft.com.pl
|
|
trisoft.com.pl
| 2 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 7, KeyTag 45126, DigestType 1 and Digest oR/iLsozm457APLHq7KLlKmDUq0=
|
|
|
|
|
| DS with Algorithm 7, KeyTag 45126, DigestType 2 and Digest bB5kI+EK+lRo6qif9R5uu+mnGBLlFvqOSG5YmSdT2NE=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner trisoft.com.pl., Algorithm: 8, 3 Labels, original TTL: 86400 sec, Signature-expiration: 16.03.2021, 12:00:00 +, Signature-Inception: 14.02.2021, 12:00:00 +, KeyTag 28974, Signer-Name: com.pl
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 28974 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 7, KeyTag 38660, Flags 256
|
|
|
|
|
| Public Key with Algorithm 7, KeyTag 45126, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 2 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner trisoft.com.pl., Algorithm: 7, 3 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| RRSIG-Owner trisoft.com.pl., Algorithm: 7, 3 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 45126, Signer-Name: trisoft.com.pl
|
|
|
|
|
| • Status: Good - Algorithmus 7 and DNSKEY with KeyTag 38660 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Good - Algorithmus 7 and DNSKEY with KeyTag 45126 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 45126, DigestType 1 and Digest "oR/iLsozm457APLHq7KLlKmDUq0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 45126, DigestType 2 and Digest "bB5kI+EK+lRo6qif9R5uu+mnGBLlFvqOSG5YmSdT2NE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: trzeci.trisoft.com.pl
|
|
trzeci.trisoft.com.pl
| 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 "jd43njbkdoqgpoqb80v7io6n0m4n89k6" between the hashed NSEC3-owner "jd43njbkdoqgpoqb80v7io6n0m4n89k6" and the hashed NextOwner "jkdg8qu0jqfpa303at16qfj8siidnpnr". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| 0 DNSKEY RR found
|
|
|
|
|
|
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 51.38.233.225
Validated: RRSIG-Owner trzeci.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "jd43njbkdoqgpoqb80v7io6n0m4n89k6" equal the hashed NSEC3-owner "jd43njbkdoqgpoqb80v7io6n0m4n89k6" and the hashed NextOwner "jkdg8qu0jqfpa303at16qfj8siidnpnr". 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 jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TXT-Query sends a valid NSEC3 RR as result with the hashed query name "jd43njbkdoqgpoqb80v7io6n0m4n89k6" equal the hashed NSEC3-owner "jd43njbkdoqgpoqb80v7io6n0m4n89k6" and the hashed NextOwner "jkdg8qu0jqfpa303at16qfj8siidnpnr". 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 jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "jd43njbkdoqgpoqb80v7io6n0m4n89k6" equal the hashed NSEC3-owner "jd43njbkdoqgpoqb80v7io6n0m4n89k6" and the hashed NextOwner "jkdg8qu0jqfpa303at16qfj8siidnpnr". 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 jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| TLSA-Query (_443._tcp.trzeci.trisoft.com.pl) sends a valid NSEC3 RR as result with the hashed owner name "jd43njbkdoqgpoqb80v7io6n0m4n89k6" (unhashed: trzeci.trisoft.com.pl). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
|
|
|
| TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "qin86avjub5np47vfvprikm44bjpfihc" (unhashed: _tcp.trzeci.trisoft.com.pl) with the owner "pavvtld3vn79mmlscotuhq8rckesd1s4" and the NextOwner "r975cjc4hruqtsqkth7vht3oiks734bp". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner pavvtld3vn79mmlscotuhq8rckesd1s4.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| 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 "urlaeb1eia8b8acokipn0oj14uc6qj51" (unhashed: *.trzeci.trisoft.com.pl) with the owner "tkrhkuln1r8m3uk4jt8n1mqd016q2s95" and the NextOwner "v2muhrrnj177hluhpeq6e8c5mo0taj4p". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, RRSIG Validated: RRSIG-Owner tkrhkuln1r8m3uk4jt8n1mqd016q2s95.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| Status: Good. NXDomain-Proof required and found.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed query name "jd43njbkdoqgpoqb80v7io6n0m4n89k6" equal the hashed NSEC3-owner "jd43njbkdoqgpoqb80v7io6n0m4n89k6" and the hashed NextOwner "jkdg8qu0jqfpa303at16qfj8siidnpnr". 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 jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.trzeci.trisoft.com.pl
|
|
www.trzeci.trisoft.com.pl
| 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 "k2v4po4000q474tp9c9vmka766fmec1a" between the hashed NSEC3-owner "jkdg8qu0jqfpa303at16qfj8siidnpnr" and the hashed NextOwner "l2ig4crdp64gm1a65huluc7klj0h048u". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner jkdg8qu0jqfpa303at16qfj8siidnpnr.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "jd43njbkdoqgpoqb80v7io6n0m4n89k6" as Owner. That's the Hash of "trzeci.trisoft.com.pl" with the NextHashedOwnerName "jkdg8qu0jqfpa303at16qfj8siidnpnr". So that domain name is the Closest Encloser of "www.trzeci.trisoft.com.pl". Opt-Out: True.
Bitmap: A, RRSIG Validated: RRSIG-Owner jd43njbkdoqgpoqb80v7io6n0m4n89k6.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|
|
|
|
|
| The ClosestEncloser says, that "*.trzeci.trisoft.com.pl" with the Hash "urlaeb1eia8b8acokipn0oj14uc6qj51" 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 "tkrhkuln1r8m3uk4jt8n1mqd016q2s95" and the Next Owner "v2muhrrnj177hluhpeq6e8c5mo0taj4p", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: A, RRSIG Validated: RRSIG-Owner tkrhkuln1r8m3uk4jt8n1mqd016q2s95.trisoft.com.pl., Algorithm: 7, 4 Labels, original TTL: 38400 sec, Signature-expiration: 14.03.2021, 23:31:02 +, Signature-Inception: 12.02.2021, 23:31:02 +, KeyTag 38660, Signer-Name: trisoft.com.pl
|