gov.ly
Updated:
2023-03-03 10:21:32 UTC (673 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- gov.ly/A (NODATA)
- gov.ly/AAAA (NODATA)
- ly/SOA
- ly/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of gov.ly/A
- NSEC3 proving non-existence of gov.ly/AAAA
- ly/DNSKEY (alg 8, id 29800)
- ly/DNSKEY (alg 8, id 60760)
- ly/DNSKEY (alg 8, id 62311)
- ly/DS (alg 8, id 62311)
Delegation status
Secure (1)
- . to ly
Notices
Errors (6)
- NSEC3 proving non-existence of gov.ly/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 gov.ly/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 gov.ly/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 gov.ly/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- ly zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:43f8:120::24)
- ly/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of gov.ly/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of gov.ly/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of gov.ly/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of gov.ly/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- ly/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
