View on GitHub

DNSViz: A DNS visualization tool

fj

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

RRset statusRRset status

Insecure (2)
  • fj/NS
  • fj/SOA
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • NSEC proving non-existence of fj/DS

Delegation statusDelegation status

Insecure (1)
  • . to fj

NoticesNotices

Errors (10)
  • fj zone: The following NS name(s) did not resolve to address(es): manu.usp.ac.fj
  • fj zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (128.32.136.3, 128.32.136.14, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e)
  • fj zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (128.32.136.3, 128.32.136.14, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e)
  • fj/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.32.136.3, 128.32.136.14, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • fj/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.32.136.3, 128.32.136.14, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e, UDP_-_EDNS0_4096_D_K)
  • fj/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.32.136.3, 128.32.136.14, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e, TCP_-_EDNS0_4096_D)
  • fj/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (128.32.136.3, 128.32.136.14, 2607:f140:ffff:fffe::3, 2607:f140:ffff:fffe::e, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • y0lphj5zkm.fj/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • fj/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • fj/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • . to fj: Authoritative AAAA records exist for adns2.berkeley.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • . to fj: The following NS name(s) were found in the delegation NS RRset (i.e., in the . zone), but not in the authoritative NS RRset: adns1.berkeley.edu, adns2.berkeley.edu See RFC 1034, Sec. 4.2.2.

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