| 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 20326, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 61809, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2025, 00:00:00 +, Signature-Inception: 30.11.2025, 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
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 35456, DigestType 2 and Digest wfzIjHPMuvqi1taFdbAe11N4bNczpKI5Mk1WCX8Xkws=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.12.2025, 17:00:00 +, Signature-Inception: 02.12.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 61809 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 1753, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 10680, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 35456, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.12.2025, 12:00:00 +, Signature-Inception: 30.11.2025, 12:00:00 +, KeyTag 35456, Signer-Name: pl
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35456 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35456, DigestType 2 and Digest "wfzIjHPMuvqi1taFdbAe11N4bNczpKI5Mk1WCX8Xkws=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: notariusz-tomcza.pl
|
|
notariusz-tomcza.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 "qagi4trgma9etvs9q36ob0ukas8shero" between the hashed NSEC3-owner "qag469o593jmmnjfod9c5fb6o56v9n4i" and the hashed NextOwner "qagmr4jn6cfvedcjhp0hqbcip3v4rp35". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner qag469o593jmmnjfod9c5fb6o56v9n4i.pl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.12.2025, 12:00:00 +, Signature-Inception: 30.11.2025, 12:00:00 +, KeyTag 10680, Signer-Name: pl
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "sualaklp6ik32je6b8eqsa2pv2p834ij" as Owner. That's the Hash of "pl" with the NextHashedOwnerName "suamfpq84kpqi3kcmf1qpu1bdclbmp1b". So that domain name is the Closest Encloser of "notariusz-tomcza.pl". Opt-Out: True.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner sualaklp6ik32je6b8eqsa2pv2p834ij.pl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.12.2025, 12:00:00 +, Signature-Inception: 30.11.2025, 12:00:00 +, KeyTag 10680, Signer-Name: pl
|
|
|
|
|
| The ClosestEncloser says, that "*.pl" with the Hash "sjrigtgekuvss4t4tfvt67en6rg2pn04" 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 "sjr9ib24ausddkdaq9dh5civdcmasnd8" and the Next Owner "sjrjf56h53uhjr34ga2psljcvet7a5kj", 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: NS, DS, RRSIG Validated: RRSIG-Owner sjr9ib24ausddkdaq9dh5civdcmasnd8.pl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.12.2025, 12:00:00 +, Signature-Inception: 30.11.2025, 12:00:00 +, KeyTag 10680, Signer-Name: pl
|
|
|
Zone: www.notariusz-tomcza.pl
|
|
www.notariusz-tomcza.pl
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "sualaklp6ik32je6b8eqsa2pv2p834ij" as Owner. That's the Hash of "pl" with the NextHashedOwnerName "suamfpq84kpqi3kcmf1qpu1bdclbmp1b". So that domain name is the Closest Encloser of "www.notariusz-tomcza.pl". Opt-Out: True.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner sualaklp6ik32je6b8eqsa2pv2p834ij.pl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.12.2025, 12:00:00 +, Signature-Inception: 30.11.2025, 12:00:00 +, KeyTag 10680, Signer-Name: pl
|
|
|
|
|
| The ClosestEncloser says, that "*.pl" with the Hash "sjrigtgekuvss4t4tfvt67en6rg2pn04" 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 "sjr9ib24ausddkdaq9dh5civdcmasnd8" and the Next Owner "sjrjf56h53uhjr34ga2psljcvet7a5kj", 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: NS, DS, RRSIG Validated: RRSIG-Owner sjr9ib24ausddkdaq9dh5civdcmasnd8.pl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.12.2025, 12:00:00 +, Signature-Inception: 30.11.2025, 12:00:00 +, KeyTag 10680, Signer-Name: pl
|