gov.lv
Updated:
2023-02-11 13:54:43 UTC (681 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- gov.lv/A
- gov.lv/MX
- gov.lv/NS
- gov.lv/SOA
- gov.lv/TXT
Secure (1)
- lv/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of gov.lv/DS
- lv/DNSKEY (alg 8, id 31113)
- lv/DNSKEY (alg 8, id 42018)
- lv/DS (alg 8, id 42018)
Delegation status
Insecure (1)
- lv to gov.lv
Secure (1)
- . to lv
Notices
Errors (6)
- NSEC3 proving non-existence of gov.lv/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 gov.lv/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- gov.lv zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (212.70.163.100, 212.70.163.230)
- gov.lv/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (212.70.163.100, 212.70.163.230, UDP_-_NOEDNS_)
- gov.lv/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (212.70.163.100, 212.70.163.230, UDP_-_NOEDNS_)
- gov.lv/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of gov.lv/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of gov.lv/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gov.lv/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
