www.moea.gov.tw
Updated:
2023-06-08 08:24:16 UTC (457 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- hinet.net/SOA
- www-moea.cdn.hinet.net/A
- www.moea.gov.tw/CNAME
Secure (3)
- gov.tw/SOA
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of hinet.net/DS
- NSEC3 proving non-existence of moea.gov.tw/DS
- gov.tw/DNSKEY (alg 8, id 19435)
- gov.tw/DNSKEY (alg 8, id 20970)
- gov.tw/DNSKEY (alg 8, id 42045)
- gov.tw/DS (alg 8, id 19435)
- gov.tw/DS (alg 8, id 514)
- net/DNSKEY (alg 8, id 27554)
- net/DNSKEY (alg 8, id 35886)
- net/DS (alg 8, id 35886)
- tw/DNSKEY (alg 8, id 42795)
- tw/DNSKEY (alg 8, id 51277)
- tw/DS (alg 8, id 51277)
Non_existent (1)
- gov.tw/DNSKEY (alg 8, id 514)
Delegation status
Insecure (3)
- gov.tw to moea.gov.tw
- hinet.net to cdn.hinet.net
- net to hinet.net
Secure (3)
- . to net
- . to tw
- tw to gov.tw
Notices
Errors (4)
- NSEC3 proving non-existence of moea.gov.tw/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 moea.gov.tw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- gov.tw/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:45b1:0:5::24, 2001:45b1:0:5::25, UDP_-_EDNS0_512_D_KN)
- tw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:288:1:1006::11)
Warnings (2)
- NSEC3 proving non-existence of moea.gov.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of moea.gov.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
JavaScript is required to make the graph below interactive.
