View on GitHub

DNSViz: A DNS visualization tool

bn

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

RRset statusRRset status

Bogus (2)
  • bn/SOA
  • bn/SOA
Secure (1)
  • bn/NS

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • bn/DNSKEY (alg 8, id 26224)
  • bn/DNSKEY (alg 8, id 35616)
  • bn/DNSKEY (alg 8, id 9994)
  • bn/DS (alg 8, id 9994)

Delegation statusDelegation status

Secure (1)
  • . to bn

NoticesNotices

Errors (8)
  • RRSIG bn/SOA alg 8, id 35616: The cryptographic signature of the RRSIG RR does not properly validate.
  • RRSIG bn/SOA alg 8, id 35616: The cryptographic signature of the RRSIG RR does not properly validate.
  • bn zone: The server(s) were not responsive to queries over TCP. (202.93.214.163)
  • bn/DNSKEY: No response was received from the server over TCP (tried 7 times). (202.93.214.163, TCP_-_EDNS0_4096_D)
  • bn/NS: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. (202.93.214.163, UDP_-_NOEDNS_)
  • bn/NS: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
  • bn/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. (202.93.214.163, UDP_-_EDNS0_4096_D_KN)
  • bn/SOA: No response was received from the server over TCP (tried 3 times). (202.93.214.163, TCP_-_EDNS0_4096_D_N)

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