bnn.go.id/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (103.112.223.1, UDP_-_EDNS0_512_D_KN)
go.id zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (45.126.57.57)
go.id/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (45.126.57.57, TCP_-_EDNS0_4096_D_KN)
bnn.go.id/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
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.
go.id to bnn.go.id: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the go.id zone): nx1.sentinel.id See RFC 1034, Sec. 4.2.2.
go.id to bnn.go.id: The following NS name(s) were found in the delegation NS RRset (i.e., in the go.id zone), but not in the authoritative NS RRset: nx2.bnn.go.id See RFC 1034, Sec. 4.2.2.
bnn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.