bnn.go.id

Updated: 2022-01-25 06:47:59 UTC (982 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 9799)
bnn.go.id/DNSKEY (alg 13, id 11543)
bnn.go.id/DNSKEY (alg 13, id 46157)
bnn.go.id/DS (alg 13, id 46157)
go.id/DNSKEY (alg 10, id 25427)
go.id/DNSKEY (alg 10, id 48051)
go.id/DS (alg 10, id 48051)
id/DNSKEY (alg 8, id 22449)
id/DNSKEY (alg 8, id 26887)
id/DS (alg 8, id 26887)

go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:d::d)
id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:d::d)

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.