bnn.go.id
Updated:
2021-10-28 13:25:07 UTC (904 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- bnn.go.id/SOA
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 14748)
- ./DNSKEY (alg 8, id 20326)
- 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 (22)
- bnn.go.id zone: The server(s) did not respond authoritatively for the namespace. (103.226.218.1)
- bnn.go.id zone: The server(s) were not responsive to queries over UDP. (2001:df3:3800::903:1)
- bnn.go.id/A: No RRSIG covering the RRset was returned in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/A: No response was received from the server over UDP (tried 12 times). (2001:df3:3800::903:1, UDP_-_NOEDNS_)
- bnn.go.id/A: The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/AAAA: No RRSIG covering the RRset was returned in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/AAAA: The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/DNSKEY (alg 13, id 11543): No RRSIG covering the RRset was returned in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/DNSKEY (alg 13, id 11543): The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/DNSKEY (alg 13, id 46157): No RRSIG covering the RRset was returned in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/DNSKEY (alg 13, id 46157): The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/MX: No RRSIG covering the RRset was returned in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/MX: The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/NS: No RRSIG covering the RRset was returned in the response. (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). (2001:df3:3800::903:1, UDP_-_NOEDNS_)
- bnn.go.id/NS: The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/SOA: No RRSIG covering the RRset was returned in the response. (103.226.218.1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- bnn.go.id/SOA: The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- bnn.go.id/TXT: No RRSIG covering the RRset was returned in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/TXT: The Authoritative Answer (AA) flag was not set in the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- go.id to bnn.go.id: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- go.id to bnn.go.id: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
Warnings (14)
- RRSIG bnn.go.id/DS alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
- bnn.go.id/A: The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/AAAA: The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/DNSKEY (alg 13, id 11543): The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/DNSKEY (alg 13, id 46157): The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/MX: The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bnn.go.id/NS: The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
- bnn.go.id/SOA: The case of the query name (BnN.gO.id) was not preserved in the Question section of the response. (103.226.218.1, UDP_-_EDNS0_4096_D_KN_0x20)
- bnn.go.id/SOA: The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- bnn.go.id/TXT: The server responded with no OPT record, rather than with RCODE FORMERR. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
