| 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 54393, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.06.2026, 00:00:00 +, Signature-Inception: 11.05.2026, 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: me
|
|
me
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 45352, DigestType 2 and Digest dwjIptXXK2MhS7/1DLVFU/fgeh+l6QdL2NY8QxAthVk=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2026, 05:00:00 +, Signature-Inception: 15.05.2026, 04:00:00 +, KeyTag 54393, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 54393 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 15291, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 45352, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 49848, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 30.05.2026, 15:18:22 +, Signature-Inception: 09.05.2026, 14:18:22 +, KeyTag 45352, Signer-Name: me
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 45352 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 45352, DigestType 2 and Digest "dwjIptXXK2MhS7/1DLVFU/fgeh+l6QdL2NY8QxAthVk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: alpha-2ott.me
|
|
alpha-2ott.me
| 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 "066chn7fa055nqrpdcoe4fn9lbpch96j" between the hashed NSEC3-owner "065kcqu176m1pi9mqt6fhi08e06k626u" and the hashed NextOwner "066hto61h21bieklf8godehoipamqdiv". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 065kcqu176m1pi9mqt6fhi08e06k626u.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.05.2026, 15:18:22 +, Signature-Inception: 09.05.2026, 14:18:22 +, KeyTag 49848, Signer-Name: me
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "8erb7pqu7ah1mdb8br1ehmoiq39p1otf" as Owner. That's the Hash of "me" with the NextHashedOwnerName "8erd8e4a32vmtkvbeuu2hearq661lbv9". So that domain name is the Closest Encloser of "alpha-2ott.me". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 8erb7pqu7ah1mdb8br1ehmoiq39p1otf.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 05.06.2026, 16:53:29 +, Signature-Inception: 15.05.2026, 15:53:29 +, KeyTag 49848, Signer-Name: me
|
|
|
|
|
| The ClosestEncloser says, that "*.me" with the Hash "vm93pdo9f6sqciomvkj9iu5nm237snlu" 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 "vm8lt2i8v4ftpk5bm9e77hpk2911e6mb" and the Next Owner "vmagmurfvap9ua5o8nitotiaj1ntvmdr", 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 vm8lt2i8v4ftpk5bm9e77hpk2911e6mb.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.05.2026, 15:18:22 +, Signature-Inception: 09.05.2026, 14:18:22 +, KeyTag 49848, Signer-Name: me
|
|
|
Zone: www.alpha-2ott.me
|
|
www.alpha-2ott.me
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "8erb7pqu7ah1mdb8br1ehmoiq39p1otf" as Owner. That's the Hash of "me" with the NextHashedOwnerName "8erd8e4a32vmtkvbeuu2hearq661lbv9". So that domain name is the Closest Encloser of "www.alpha-2ott.me". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 8erb7pqu7ah1mdb8br1ehmoiq39p1otf.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 05.06.2026, 16:53:29 +, Signature-Inception: 15.05.2026, 15:53:29 +, KeyTag 49848, Signer-Name: me
|
|
|
|
|
| The ClosestEncloser says, that "*.me" with the Hash "vm93pdo9f6sqciomvkj9iu5nm237snlu" 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 "vm8lt2i8v4ftpk5bm9e77hpk2911e6mb" and the Next Owner "vmagmurfvap9ua5o8nitotiaj1ntvmdr", 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 vm8lt2i8v4ftpk5bm9e77hpk2911e6mb.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.05.2026, 15:18:22 +, Signature-Inception: 09.05.2026, 14:18:22 +, KeyTag 49848, Signer-Name: me
|