railway.gov.tw/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (163.29.186.200, 163.29.186.201, 210.241.82.200, 210.241.82.201, UDP_-_NOEDNS_)
railway.gov.tw/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (163.29.186.200, 163.29.186.201, 210.241.82.200, 210.241.82.201, UDP_-_EDNS0_512_D_KN)
railway.gov.tw/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
gov.tw to railway.gov.tw: A glue records exist for ns1.railway.gov.tw, but there are no corresponding authoritative A records. See RFC 1034, Sec. 4.2.2.
www.railway.gov.tw/A: 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. (2001:4420:60ab:1fd::6, UDP_-_EDNS0_4096_D_KN)
www.railway.gov.tw/AAAA: 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. (2001:4420:60ab:1fd::6, UDP_-_EDNS0_4096_D_KN)
railway.gov.tw/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.