gov.tn

Updated: 2023-04-20 13:16:43 UTC (629 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
gov.tn/DNSKEY (alg 8, id 34336)
gov.tn/DNSKEY (alg 8, id 64206)
gov.tn/DS (alg 8, id 34336)
gov.tn/DS (alg 8, id 34336)
tn/DNSKEY (alg 8, id 36171)
tn/DNSKEY (alg 8, id 8629)
tn/DS (alg 8, id 8629)

gov.tn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:4:41:228:62:63)
gov.tn/NS: There was an error communicating with the server over UDP (EACCES). See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:4:41:228:62:63, UDP_-_EDNS0_4096_D_KN)
tn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:4:41:228:62:63)
gov.tn/A has errors; select the "Denial of existence" DNSSEC option to see them.

gov.tn/DS (alg 8, id 34336): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov.tn/DS (alg 8, id 34336): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov.tn/DS (alg 8, id 34336): 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.tn/DS (alg 8, id 34336): 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.