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
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 20038, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 20326, 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: 31.08.2024, 00:00:00 +, Signature-Inception: 10.08.2024, 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: cloud
|
|
cloud
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 13, KeyTag 7041, DigestType 2 and Digest A+G0Exn906FOJ841/7qANtpR4ygWXOECrmmmwSA/ZOQ=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner cloud., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.08.2024, 17:00:00 +, Signature-Inception: 16.08.2024, 16:00:00 +, KeyTag 20038, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20038 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 7041, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 36804, Flags 256
|
|
|
|
|
| 2 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner cloud., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.09.2024, 08:46:21 +, Signature-Inception: 17.08.2024, 08:46:21 +, KeyTag 7041, Signer-Name: cloud
|
|
|
|
|
| RRSIG-Owner cloud., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.09.2024, 08:46:21 +, Signature-Inception: 17.08.2024, 08:46:21 +, KeyTag 36804, Signer-Name: cloud
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 7041 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 36804 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 7041, DigestType 2 and Digest "A+G0Exn906FOJ841/7qANtpR4ygWXOECrmmmwSA/ZOQ=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
Zone: xsc.cloud
|
|
xsc.cloud
| 1 DS RR in the parent zone found
|
|
|
|
|
| DS with Algorithm 13, KeyTag 47140, DigestType 2 and Digest 8e3iBFcyeijyntidySI3ZOKS92HH/3Z4cHqqAed3160=
|
|
|
|
|
| 1 RRSIG RR to validate DS RR found
|
|
|
|
|
| RRSIG-Owner xsc.cloud., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 16.09.2024, 08:46:21 +, Signature-Inception: 17.08.2024, 08:46:21 +, KeyTag 36804, Signer-Name: cloud
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 36804 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 2136, Flags 256
|
|
|
|
|
| Public Key with Algorithm 13, KeyTag 47140, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner xsc.cloud., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 47140, Signer-Name: xsc.cloud
|
|
|
|
|
| • Status: Good - Algorithmus 13 and DNSKEY with KeyTag 47140 used to validate the DNSKEY RRSet
|
|
|
|
|
| • Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 47140, DigestType 2 and Digest "8e3iBFcyeijyntidySI3ZOKS92HH/3Z4cHqqAed3160=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
|
|
|
|
|
| RRSIG Type 1 validates the A - Result: 62.163.177.65
Validated: RRSIG-Owner xsc.cloud., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| RRSIG Type 16 validates the TXT - Result: v=spf1 ~all
Validated: RRSIG-Owner xsc.cloud., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| RRSIG Type 5 validates the TLSA - Result (_443._tcp.xsc.cloud): xsc.synology.me. That's a CNAME answer. RRSIG Owner has 4 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 _443._tcp.xsc.cloud., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "mp605l4a6kg1u9ps1lje83v2hle02ud2" equal the hashed NSEC3-owner "mp605l4a6kg1u9ps1lje83v2hle02ud2" and the hashed NextOwner "ntm23gu2h1oc18bvl79l9eovc0tj7nrm". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner mp605l4a6kg1u9ps1lje83v2hle02ud2.xsc.cloud., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "mp605l4a6kg1u9ps1lje83v2hle02ud2" equal the hashed NSEC3-owner "mp605l4a6kg1u9ps1lje83v2hle02ud2" and the hashed NextOwner "ntm23gu2h1oc18bvl79l9eovc0tj7nrm". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner mp605l4a6kg1u9ps1lje83v2hle02ud2.xsc.cloud., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| Bitmap: TXT, RRSIG Validated: RRSIG-Owner gsbgmugqehuei5jkev9mlfi9pdeodqva.xsc.cloud., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
|
|
| CAA-Query sends a valid NSEC3 RR as result with the hashed query name "mp605l4a6kg1u9ps1lje83v2hle02ud2" equal the hashed NSEC3-owner "mp605l4a6kg1u9ps1lje83v2hle02ud2" and the hashed NextOwner "ntm23gu2h1oc18bvl79l9eovc0tj7nrm". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner mp605l4a6kg1u9ps1lje83v2hle02ud2.xsc.cloud., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: www.xsc.cloud
|
|
www.xsc.cloud
| 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 "b4jlts04bm7deksatljb69oprn3uha44" between the hashed NSEC3-owner "6bghl4abq694f8skc3tvslfnj46ot8uk" and the hashed NextOwner "c2d5sc9jd6kuack9l9a8mqc5k33orim6". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 6bghl4abq694f8skc3tvslfnj46ot8uk.xsc.cloud., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| RRSIG Type 5 validates the CNAME - Result: xsc.synology.me. 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.xsc.cloud., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "6bghl4abq694f8skc3tvslfnj46ot8uk" (unhashed: *.xsc.cloud) as the Wildcard-Expansion of the Closest Encloser of the query name "b4jlts04bm7deksatljb69oprn3uha44". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "b4jlts04bm7deksatljb69oprn3uha44" between the hashed NSEC3-owner "6bghl4abq694f8skc3tvslfnj46ot8uk" and the hashed NextOwner "c2d5sc9jd6kuack9l9a8mqc5k33orim6". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 6bghl4abq694f8skc3tvslfnj46ot8uk.xsc.cloud., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.08.2024, 00:00:00 +, Signature-Inception: 08.08.2024, 00:00:00 +, KeyTag 2136, Signer-Name: xsc.cloud
|
|
|
|
|
| Status: Good. NoData-Proof required and found.
|
|
|
Zone: (root)
|
|
(root)
| 1 DS RR published
|
|
|
|
|
| DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=
|
|
|
|
|
| • Status: Valid because published
|
|
|
|
|
| 2 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 20038, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 20326, 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: 31.08.2024, 00:00:00 +, Signature-Inception: 10.08.2024, 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: 29.08.2024, 17:00:00 +, Signature-Inception: 16.08.2024, 16:00:00 +, KeyTag 20038, Signer-Name: (root)
|
|
|
|
|
| • Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20038 used to validate the DS RRSet in the parent zone
|
|
|
|
|
| 3 DNSKEY RR found
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 12948, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 23718, Flags 256
|
|
|
|
|
| Public Key with Algorithm 8, KeyTag 45352, Flags 257 (SEP = Secure Entry Point)
|
|
|
|
|
| 1 RRSIG RR to validate DNSKEY RR found
|
|
|
|
|
| RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 30.08.2024, 15:31:15 +, Signature-Inception: 09.08.2024, 14:31:15 +, 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: synology.me
|
|
synology.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 "sghodq0sgkv7fohgafl0dkvuoaj6l9n3" between the hashed NSEC3-owner "sggqfpv1lk7s7ks735rnml7l88t1rudb" and the hashed NextOwner "sghsj8tfndholu0ds4bm4sak6oukdfvf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner sggqfpv1lk7s7ks735rnml7l88t1rudb.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.08.2024, 15:31:15 +, Signature-Inception: 09.08.2024, 14:31:15 +, KeyTag 23718, 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 "synology.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: 07.09.2024, 09:48:19 +, Signature-Inception: 17.08.2024, 08:48:19 +, KeyTag 23718, Signer-Name: me
|
|
|
|
|
| 0 DNSKEY RR found
|
|
|
|
|
|
|
|
|
Zone: xsc.synology.me
|
|
xsc.synology.me
| 0 DS RR in the parent zone found
|
|
|
|
|
| 0 DNSKEY RR found
|
|
|
|
|
|
|