argenta.be
Updated:
2022-09-26 09:15:31 UTC (820 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- argenta.be/A
- argenta.be/MX
- argenta.be/NS
- argenta.be/SOA
- argenta.be/TXT
Secure (1)
- be/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of argenta.be/DS
- be/DNSKEY (alg 8, id 12664)
- be/DNSKEY (alg 8, id 25494)
- be/DNSKEY (alg 8, id 46029)
- be/DNSKEY (alg 8, id 52756)
- be/DNSKEY (alg 8, id 53301)
- be/DS (alg 8, id 12664)
- be/DS (alg 8, id 52756)
Delegation status
Insecure (1)
- be to argenta.be
Secure (1)
- . to be
Notices
Errors (4)
- NSEC3 proving non-existence of argenta.be/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of argenta.be/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- be zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:68::1)
- argenta.be/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of argenta.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of argenta.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- argenta.be/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
