| 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 21831, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 38696, 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: 03.03.2026, 00:00:00 +, Signature-Inception: 10.02.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: ai
|
|
ai
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 8, KeyTag 3799, DigestType 2 and Digest ioAw1GYa5vz0FzSWgqwFhkg3EALnDnF+TPLxH4NUM4U=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner ai., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 26.02.2026, 21:00:00 +, Signature-Inception: 13.02.2026, 20:00:00 +, KeyTag 21831, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 21831 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 4 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 3799, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 4644, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 6279, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 44137, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner ai., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 02.03.2026, 15:31:56 +, Signature-Inception: 09.02.2026, 14:31:56 +, KeyTag 3799, Signer-Name: ai
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 3799 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 3799, DigestType 2 and Digest "ioAw1GYa5vz0FzSWgqwFhkg3EALnDnF+TPLxH4NUM4U=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: ramphan.ai
|
|
ramphan.ai
| 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 "seqmbal74c4v5rhefjrs2q6dplrcuk6a" between the hashed NSEC3-owner "seqerh21v5jin57eclg9e66sg7htbrbb" and the hashed NextOwner "servnhu705tl6tpfp0l723ik51glg70a". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner seqerh21v5jin57eclg9e66sg7htbrbb.ai., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.03.2026, 15:31:56 +, Signature-Inception: 09.02.2026, 14:31:56 +, KeyTag 6279, Signer-Name: ai
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "58cj07tk4r4uuu6m10c83sia655jfil6" as Owner. That's the Hash of "ai" with the NextHashedOwnerName "58e5j7rfab1b4k4bbvck7i2eta2o1qkp". So that domain name is the Closest Encloser of "ramphan.ai". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 58cj07tk4r4uuu6m10c83sia655jfil6.ai., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.03.2026, 03:07:32 +, Signature-Inception: 14.02.2026, 02:07:32 +, KeyTag 6279, Signer-Name: ai
|
|
|
|
|
| The ClosestEncloser says, that "*.ai" with the Hash "19d7f007jo4tpmqp085kdrkae9vnturm" 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 "19ctkokutmnlva3rjh3ovhgvi3tvn7dm" and the Next Owner "19d8lr9ldef3nk7l0kmkst1q40g90flv", 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 19ctkokutmnlva3rjh3ovhgvi3tvn7dm.ai., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.03.2026, 15:31:56 +, Signature-Inception: 09.02.2026, 14:31:56 +, KeyTag 6279, Signer-Name: ai
|
|
|
Zone: www.ramphan.ai
|
|
www.ramphan.ai
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "58cj07tk4r4uuu6m10c83sia655jfil6" as Owner. That's the Hash of "ai" with the NextHashedOwnerName "58e5j7rfab1b4k4bbvck7i2eta2o1qkp". So that domain name is the Closest Encloser of "www.ramphan.ai". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 58cj07tk4r4uuu6m10c83sia655jfil6.ai., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.03.2026, 03:07:32 +, Signature-Inception: 14.02.2026, 02:07:32 +, KeyTag 6279, Signer-Name: ai
|
|
|
|
|
| The ClosestEncloser says, that "*.ai" with the Hash "19d7f007jo4tpmqp085kdrkae9vnturm" 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 "19ctkokutmnlva3rjh3ovhgvi3tvn7dm" and the Next Owner "19d8lr9ldef3nk7l0kmkst1q40g90flv", 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 19ctkokutmnlva3rjh3ovhgvi3tvn7dm.ai., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.03.2026, 15:31:56 +, Signature-Inception: 09.02.2026, 14:31:56 +, KeyTag 6279, Signer-Name: ai
|