org.gl
Updated:
2022-10-06 16:03:50 UTC (770 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- gl/SOA
- org.gl/A (NODATA)
- org.gl/AAAA (NODATA)
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of org.gl/A
- NSEC3 proving non-existence of org.gl/AAAA
- gl/DNSKEY (alg 8, id 11560)
- gl/DNSKEY (alg 8, id 42900)
- gl/DS (alg 8, id 11560)
Delegation status
Secure (1)
- . to gl
Notices
Errors (5)
- NSEC3 proving non-existence of org.gl/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 org.gl/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 org.gl/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 org.gl/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- gl/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of org.gl/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of org.gl/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of org.gl/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of org.gl/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gl/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
