gouv.tg
Updated:
2024-04-28 06:37:51 UTC (251 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- gouv.tg/A
- gouv.tg/MX
- gouv.tg/NS
- gouv.tg/SOA
- gouv.tg/TXT
- tg/SOA
Secure (1)
- ./SOA
DNSKEY/DS/NSEC status
Secure (3)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- NSEC proving non-existence of tg/DS
Delegation status
Insecure (2)
- . to tg
- tg to gouv.tg
Notices
Errors (2)
- gouv.tg zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (80.248.64.20)
- tg zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (108.61.25.122, 2001:19f0:300:1007::cafe, 2001:41d0:2:8adf::2, 2001:41d0:8:5c79::3)
Warnings (5)
- . to tg: Authoritative AAAA records exist for ns1.admin.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- . to tg: The glue address(es) for ns2.admin.net (108.61.25.122) differed from its authoritative address(es) (128.199.117.237). See RFC 1034, Sec. 4.2.2.
- . to tg: The glue address(es) for ns2.admin.net (2001:19f0:300:1007::cafe) differed from its authoritative address(es) (2400:6180:0:d0::2ae:5001). See RFC 1034, Sec. 4.2.2.
- . to tg: The glue address(es) for ns3.admin.net (2001:41d0:2:8adf::2) differed from its authoritative address(es) (2001:41d0:304:200::6085). See RFC 1034, Sec. 4.2.2.
- . to tg: The glue address(es) for ns5.admin.net (2001:41d0:8:5c79::3) differed from its authoritative address(es) (2001:41d0:401:3000::86a). See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
