rodier.me
Updated:
2023-04-29 13:50:45 UTC (602 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- me/SOA
- rodier.me/A (NODATA)
- rodier.me/AAAA (NODATA)
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of rodier.me/A
- NSEC3 proving non-existence of rodier.me/AAAA
- me/DNSKEY (alg 8, id 29439)
- me/DNSKEY (alg 8, id 45352)
- me/DNSKEY (alg 8, id 7335)
- me/DS (alg 8, id 45352)
Delegation status
Secure (1)
- . to me
Notices
Errors (6)
- NSEC3 proving non-existence of rodier.me/A: 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 rodier.me/A: 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 rodier.me/AAAA: 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 rodier.me/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- me zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:54::1)
- me/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of rodier.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of rodier.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of rodier.me/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of rodier.me/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- me/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
