| 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
|
|
|
|
|
| 4 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 8763, Flags 256
|
|
|
|
|
| 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 57780, Flags 256
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.10.2026, 00:00:00 +, Signature-Inception: 01.10.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: ie
|
|
ie
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 13, KeyTag 5150, DigestType 2 and Digest h4P688waSCY48agiqStqD/t5GrKkQiMneKyr/KJv6jE=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner ie., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.10.2026, 05:00:00 +, Signature-Inception: 02.10.2026, 04:00:00 +, KeyTag 8763, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 8763 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 5150, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 13864, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 16958, Flags 256
|
|
|
|
|
| 2 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner ie., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 22.10.2026, 02:36:25 +, Signature-Inception: 23.09.2026, 16:01:14 +, KeyTag 5150, Signer-Name: ie
|
|
|
|
|
| RRSIG-Owner ie., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 22.10.2026, 02:36:25 +, Signature-Inception: 23.09.2026, 16:01:14 +, KeyTag 13864, Signer-Name: ie
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 5150 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 13864 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 5150, DigestType 2 and Digest "h4P688waSCY48agiqStqD/t5GrKkQiMneKyr/KJv6jE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: hubin.ie
|
|
hubin.ie
| 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 "i97fh8stbfh18svbtsi7q4v2d8cm4816" between the hashed NSEC3-owner "i968idpl9edjipturdvlfm01sai1cabk" and the hashed NextOwner "ia6gjtmqp6kt3sgh398t6dhr7u3hggl4". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner i968idpl9edjipturdvlfm01sai1cabk.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.10.2026, 05:03:42 +, Signature-Inception: 30.09.2026, 17:01:10 +, KeyTag 16958, Signer-Name: ie
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "lvac8hnh01gjt6ifv2v8aaqh8emaml8d" as Owner. That's the Hash of "ie" with the NextHashedOwnerName "lvfcc3oih8bgdrvcqrhlctr6p9lnrli9". So that domain name is the Closest Encloser of "hubin.ie". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner lvac8hnh01gjt6ifv2v8aaqh8emaml8d.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.10.2026, 23:19:20 +, Signature-Inception: 30.09.2026, 07:01:18 +, KeyTag 16958, Signer-Name: ie
|
|
|
|
|
| The ClosestEncloser says, that "*.ie" with the Hash "pp909p0vmdhnt0hghudce42f08midr2q" 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 "pp3snql6lol3551275sheh23008r9dku" and the Next Owner "pq315la6oqu1qmb6pbbiegg6rcr41moa", 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 pp3snql6lol3551275sheh23008r9dku.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.10.2026, 03:55:03 +, Signature-Inception: 30.09.2026, 14:01:13 +, KeyTag 16958, Signer-Name: ie
|
|
|
Zone: app.hubin.ie
|
|
app.hubin.ie
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "lvac8hnh01gjt6ifv2v8aaqh8emaml8d" as Owner. That's the Hash of "ie" with the NextHashedOwnerName "lvfcc3oih8bgdrvcqrhlctr6p9lnrli9". So that domain name is the Closest Encloser of "app.hubin.ie". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner lvac8hnh01gjt6ifv2v8aaqh8emaml8d.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.10.2026, 23:19:20 +, Signature-Inception: 30.09.2026, 07:01:18 +, KeyTag 16958, Signer-Name: ie
|
|
|
|
|
| The ClosestEncloser says, that "*.ie" with the Hash "pp909p0vmdhnt0hghudce42f08midr2q" 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 "pp3snql6lol3551275sheh23008r9dku" and the Next Owner "pq315la6oqu1qmb6pbbiegg6rcr41moa", 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 pp3snql6lol3551275sheh23008r9dku.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.10.2026, 03:55:03 +, Signature-Inception: 30.09.2026, 14:01:13 +, KeyTag 16958, Signer-Name: ie
|
|
|
Zone: www.app.hubin.ie
|
|
www.app.hubin.ie
| 0 DS RR in the parent zone found
|
|
|
|
|
| DS-Query in the parent zone sends valid NSEC3 RR with the Hash "lvac8hnh01gjt6ifv2v8aaqh8emaml8d" as Owner. That's the Hash of "ie" with the NextHashedOwnerName "lvfcc3oih8bgdrvcqrhlctr6p9lnrli9". So that domain name is the Closest Encloser of "www.app.hubin.ie". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner lvac8hnh01gjt6ifv2v8aaqh8emaml8d.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 27.10.2026, 23:19:20 +, Signature-Inception: 30.09.2026, 07:01:18 +, KeyTag 16958, Signer-Name: ie
|
|
|
|
|
| The ClosestEncloser says, that "*.ie" with the Hash "pp909p0vmdhnt0hghudce42f08midr2q" 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 "pp3snql6lol3551275sheh23008r9dku" and the Next Owner "pq315la6oqu1qmb6pbbiegg6rcr41moa", 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 pp3snql6lol3551275sheh23008r9dku.ie., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.10.2026, 03:55:03 +, Signature-Inception: 30.09.2026, 14:01:13 +, KeyTag 16958, Signer-Name: ie
|