View on GitHub

DNSViz: A DNS visualization tool

bnn.go.id

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset 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 statusDNSKEY/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 statusDelegation status

Secure (3)
  • . to id
  • go.id to bnn.go.id
  • id to go.id

NoticesNotices

Errors (26)
  • bnn.go.id zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (103.226.218.1)
  • bnn.go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:df3:3800::903:1)
  • bnn.go.id/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (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). See RFC 1035, Sec. 4.2. (2001:df3:3800::903:1, UDP_-_NOEDNS_)
  • bnn.go.id/A: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
  • bnn.go.id/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
  • bnn.go.id/AAAA: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (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. See RFC 4035, Sec. 3.1.1. (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. See RFC 1035, Sec. 4.1.1. (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. See RFC 4035, Sec. 3.1.1. (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. See RFC 1035, Sec. 4.1.1. (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. See RFC 4035, Sec. 3.1.1. (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. See RFC 1035, Sec. 4.1.1. (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. See RFC 4035, Sec. 3.1.1. (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 Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
  • bnn.go.id/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (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. See RFC 1035, Sec. 4.1.1. (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. See RFC 4035, Sec. 3.1.1. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
  • bnn.go.id/TXT: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (103.226.218.1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • bnn.go.id/CNAME 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/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • sl7vtm32yn.bnn.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
  • 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/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (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. See RFC 6891, Sec. 7. (103.226.218.1, UDP_-_EDNS0_4096_D_KN)
  • bnn.go.id/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bnn.go.id/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bnn.go.id/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bnn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sl7vtm32yn.bnn.go.id/A has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph