bnn.go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.226.218.1, 2001:df3:3800::903:1)
bnn.go.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:df3:3800::903:1, UDP_-_NOEDNS_)
bnn.go.id/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
bnn.go.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:df3:3800::903:1, UDP_-_NOEDNS_)
bnn.go.id/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
Warnings (6)
RRSIG bnn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
bnn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.