bnn.go.id
Updated:
2024-11-15 06:40:35 UTC (36 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- bnn.go.id/A
- bnn.go.id/AAAA
- bnn.go.id/MX
- bnn.go.id/NS
- bnn.go.id/SOA
- bnn.go.id/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- 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)
Delegation status
Secure (3)
- . to id
- go.id to bnn.go.id
- id to go.id
Notices
Errors (18)
- bnn.go.id zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1)
- bnn.go.id zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1)
- bnn.go.id/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_)
- bnn.go.id/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_)
- bnn.go.id/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- bnn.go.id/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- bnn.go.id/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_)
- bnn.go.id/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, TCP_-_NOEDNS_)
- bnn.go.id/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- bnn.go.id/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_)
- go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, 2402:ee80:c::c, 2402:ee80:d::d)
- id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:df5:4000:4::4, 2402:ee80:c::c, 2402:ee80:d::d)
- bnn.go.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- bnn.go.id/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- bnn.go.id/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 69jvx.lrcos.bnn.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
- bnn.go.id/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- bnn.go.id/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- 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 glue address(es) for nx2.bnn.go.id (103.112.223.1) differed from its authoritative address(es) (223.27.149.70). See RFC 1034, Sec. 4.2.2.
- go.id to bnn.go.id: The glue address(es) for nx2.bnn.go.id (2001:df4:bd00::990:1) differed from its authoritative address(es) (2401:2400:4:2::70). See RFC 1034, Sec. 4.2.2.
- bnn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
