gov.tn
Updated:
2024-02-22 15:29:53 UTC (317 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- gov.tn/MX
- gov.tn/NS
- gov.tn/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- 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)
Delegation status
Secure (2)
- . to tn
- tn to gov.tn
Notices
Warnings (6)
- ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (170.247.170.2, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 30903): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (170.247.170.2, UDP_-_EDNS0_4096_D_KN)
- 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.
JavaScript is required to make the graph below interactive.
