rezosup.org
Updated:
2021-04-13 16:06:50 UTC (1318 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- rezosup.org/A
- rezosup.org/AAAA
- rezosup.org/MX
- rezosup.org/NS
- rezosup.org/SOA
- rezosup.org/TXT
Secure (2)
- org/SOA
- org/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- rezosup.org/DNSKEY (alg 14, id 18901)
- rezosup.org/DNSKEY (alg 14, id 40211)
Secure (7)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of rezosup.org/DS
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 27558)
- org/DNSKEY (alg 8, id 30453)
- org/DS (alg 8, id 26974)
Delegation status
Insecure (1)
- org to rezosup.org
Secure (1)
- . to org
Notices
Errors (4)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
- NSEC3 proving non-existence of rezosup.org/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 rezosup.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- rezosup.org/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of rezosup.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of rezosup.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- rezosup.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
