Zone (*) DNSSEC - Informations Zone : (root)(root) 1 DS RR published DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=
• Status: Valid because published3 DNSKEY RR found Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)
Public Key with Algorithm 8, KeyTag 20826, Flags 256
Public Key with Algorithm 8, KeyTag 47671, Flags 256
1 RRSIG RR to validate DNSKEY RR found RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2022, 00:00:00 +, Signature-Inception: 20.06.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 zoneZone : coco 2 DS RR in the parent zone found DS with Algorithm 8, KeyTag 43834, DigestType 2 and Digest poYC7DDE5fXTOmJNNVSaf2osk5OdSyELqPpITzsOCE4=
DS with Algorithm 8, KeyTag 61744, DigestType 2 and Digest ua3Kh0U8H2mppSRoH0F5qIN0xUakWJKswQ4mU1GazL0=
1 RRSIG RR to validate DS RR found RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.07.2022, 05:00:00 +, Signature-Inception: 23.06.2022, 04:00:00 +, KeyTag 47671, Signer-Name: (root)
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 47671 used to validate the DS RRSet in the parent zone4 DNSKEY RR found Public Key with Algorithm 8, KeyTag 19065, Flags 256
Public Key with Algorithm 8, KeyTag 43834, Flags 257 (SEP = Secure Entry Point)
Public Key with Algorithm 8, KeyTag 61744, Flags 257 (SEP = Secure Entry Point)
Public Key with Algorithm 8, KeyTag 64278, Flags 256
3 RRSIG RR to validate DNSKEY RR found RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 20.07.2022, 01:44:00 +, Signature-Inception: 20.06.2022, 00:52:26 +, KeyTag 19065, Signer-Name: co
RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 20.07.2022, 01:44:00 +, Signature-Inception: 20.06.2022, 00:52:26 +, KeyTag 43834, Signer-Name: co
RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 20.07.2022, 01:44:00 +, Signature-Inception: 20.06.2022, 00:52:26 +, KeyTag 61744, Signer-Name: co
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 19065 used to validate the DNSKEY RRSet• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 43834 used to validate the DNSKEY RRSet• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 61744 used to validate the DNSKEY RRSet• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 43834, DigestType 2 and Digest "poYC7DDE5fXTOmJNNVSaf2osk5OdSyELqPpITzsOCE4=" 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 8, KeyTag 61744, DigestType 2 and Digest "ua3Kh0U8H2mppSRoH0F5qIN0xUakWJKswQ4mU1GazL0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zoneZone : x28.cox28.co 1 DS RR in the parent zone found DS with Algorithm 8, KeyTag 26636, DigestType 2 and Digest cShhbaYy0V2jiuU3FMV1PyCYGvdTJZjL90V/NmQOJf0=
1 RRSIG RR to validate DS RR found RRSIG-Owner x28.co., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 23.07.2022, 07:38:00 +, Signature-Inception: 23.06.2022, 06:38:00 +, KeyTag 19065, Signer-Name: co
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 19065 used to validate the DS RRSet in the parent zone2 DNSKEY RR found Public Key with Algorithm 8, KeyTag 25324, Flags 256
Public Key with Algorithm 8, KeyTag 26636, Flags 257 (SEP = Secure Entry Point)
1 RRSIG RR to validate DNSKEY RR found RRSIG-Owner x28.co., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 26636, Signer-Name: x28.co
• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26636 used to validate the DNSKEY RRSet• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26636, DigestType 2 and Digest "cShhbaYy0V2jiuU3FMV1PyCYGvdTJZjL90V/NmQOJf0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zoneRRSIG Type 1 validates the A - Result: 188.166.198.213 Validated: RRSIG-Owner x28.co., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "n53fk86t3sr017png0k2d5p92p818bii" equal the hashed NSEC3-owner "n53fk86t3sr017png0k2d5p92p818bii" and the hashed NextOwner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TXT-Query sends a valid NSEC3 RR as result with the hashed query name "n53fk86t3sr017png0k2d5p92p818bii" equal the hashed NSEC3-owner "n53fk86t3sr017png0k2d5p92p818bii" and the hashed NextOwner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". 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, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "n53fk86t3sr017png0k2d5p92p818bii" equal the hashed NSEC3-owner "n53fk86t3sr017png0k2d5p92p818bii" and the hashed NextOwner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". 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, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TLSA-Query (_443._tcp.x28.co) sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "889qq63loesmqvqkn0k2ud4lj1kfm02d" (unhashed: _tcp.x28.co) with the owner "n53fk86t3sr017png0k2d5p92p818bii" and the NextOwner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.x28.co) sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "9u778k3t9rulb5r5mbsulces0bulbqkh" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" (unhashed: *.x28.co) as the Wildcard-Expansion of the Closest Encloser of the query name "9u778k3t9rulb5r5mbsulces0bulbqkh". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. CAA-Query sends a valid NSEC3 RR as result with the hashed query name "n53fk86t3sr017png0k2d5p92p818bii" equal the hashed NSEC3-owner "n53fk86t3sr017png0k2d5p92p818bii" and the hashed NextOwner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". 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, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. Zone : www.x28.cowww.x28.co 0 DS RR in the parent zone found DS-Query in the parent zone sends valid NSEC3 RR with the Hash "n53fk86t3sr017png0k2d5p92p818bii" as Owner. That's the Hash of "x28.co" with the NextHashedOwnerName "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". So that domain name is the Closest Encloser of "www.x28.co". Opt-Out: False.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
The ClosestEncloser says, that "*.x28.co" with the Hash "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" 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 "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" and the Next Owner "n53fk86t3sr017png0k2d5p92p818bii", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
The ClosestEncloser says, that "*.x28.co" with the Hash "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" 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 "n53fk86t3sr017png0k2d5p92p818bii" and the Next Owner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
RRSIG Type 1 validates the A - Result: 188.166.198.213. RRSIG Owner has 3 labels, RRSIG Labels = 2, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name. Validated: RRSIG-Owner www.x28.co., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
A-Query sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. A-Query sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "ojfore1ones1nfcki6qt54kklvql8mhk" comes after the hashed Owner, so the zone confirmes the not-existence of that A RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. CNAME-Query sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "ojfore1ones1nfcki6qt54kklvql8mhk" comes after the hashed Owner, so the zone confirmes the not-existence of that CNAME RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" (unhashed: *.x28.co) as the Wildcard-Expansion of the Closest Encloser of the query name "ojfore1ones1nfcki6qt54kklvql8mhk". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. TXT-Query sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "ojfore1ones1nfcki6qt54kklvql8mhk" comes after the hashed Owner, so the zone confirmes the not-existence of that TXT RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" (unhashed: *.x28.co) as the Wildcard-Expansion of the Closest Encloser of the query name "ojfore1ones1nfcki6qt54kklvql8mhk". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. AAAA-Query sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "ojfore1ones1nfcki6qt54kklvql8mhk" comes after the hashed Owner, so the zone confirmes the not-existence of that AAAA RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" (unhashed: *.x28.co) as the Wildcard-Expansion of the Closest Encloser of the query name "ojfore1ones1nfcki6qt54kklvql8mhk". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TLSA-Query (_443._tcp.www.x28.co) sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ojfore1ones1nfcki6qt54kklvql8mhk" (unhashed: www.x28.co) with the owner "n53fk86t3sr017png0k2d5p92p818bii" and the NextOwner "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query (_443._tcp.www.x28.co) sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "8pec81onommecppej3q7k9m4ehqqsfni" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" (unhashed: *.x28.co) as the Wildcard-Expansion of the Closest Encloser of the query name "8pec81onommecppej3q7k9m4ehqqsfni". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "n53fk86t3sr017png0k2d5p92p818bii" (unhashed: x28.co). So that's the Closest Encloser of the query name. CAA-Query sends a valid NSEC3 RR as result with the owner name "n53fk86t3sr017png0k2d5p92p818bii" greater the NextOwner-Name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45", so the NSEC3 covers the end of the zone. The hashed query name "ojfore1ones1nfcki6qt54kklvql8mhk" comes after the hashed Owner, so the zone confirmes the not-existence of that CAA RR.Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner n53fk86t3sr017png0k2d5p92p818bii.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found. CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "bh6tbgqllg22sn6l5e0jf8n4hlqm9p45" (unhashed: *.x28.co) as the Wildcard-Expansion of the Closest Encloser of the query name "ojfore1ones1nfcki6qt54kklvql8mhk". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG Validated: RRSIG-Owner bh6tbgqllg22sn6l5e0jf8n4hlqm9p45.x28.co., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 14.07.2022, 07:29:11 +, Signature-Inception: 22.06.2022, 07:29:11 +, KeyTag 25324, Signer-Name: x28.co
Status: Good. NoData-Proof required and found.