gov.si
Updated:
2024-02-14 10:05:39 UTC (312 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- gov.si/A
- gov.si/AAAA
- gov.si/MX
- gov.si/NS
- gov.si/NSEC3PARAM
- gov.si/SOA
- gov.si/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- gov.si/DNSKEY (alg 8, id 36870)
- gov.si/DNSKEY (alg 8, id 38073)
- gov.si/DNSKEY (alg 8, id 44047)
- gov.si/DS (alg 8, id 44047)
- gov.si/DS (alg 8, id 44047)
- si/DNSKEY (alg 8, id 45546)
- si/DNSKEY (alg 8, id 53074)
- si/DS (alg 8, id 53074)
Delegation status
Secure (2)
- . to si
- si to gov.si
Notices
Errors (2)
- 5bsy1x8v9q.gov.si/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.si/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- gov.si/DS (alg 8, id 44047): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov.si/DS (alg 8, id 44047): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov.si/DS (alg 8, id 44047): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- gov.si/DS (alg 8, id 44047): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- si to gov.si: Authoritative AAAA records exist for ns1s.gov.si, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- si to gov.si: Authoritative AAAA records exist for ns2s.gov.si, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- 5bsy1x8v9q.gov.si/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- gov.si/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
