View on GitHub

DNSViz: A DNS visualization tool

rutgers.edu

Updated: 2018-11-08 02:45:05 UTC (133 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • rutgers.edu/A
  • rutgers.edu/MX
  • rutgers.edu/NS
  • rutgers.edu/SOA
  • rutgers.edu/TXT
Secure (2)
  • edu/SOA
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 19036)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 2134)
  • NSEC3 proving non-existence of rutgers.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 37217)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

Insecure (1)
  • edu to rutgers.edu
Secure (1)
  • . to edu

NoticesNotices

Errors (2)
  • rutgers.edu zone: The server(s) were not responsive to queries over TCP. (2a02:e980:4::57, 2a02:e980:5::8, 2a02:e980:6::7c)
  • rutgers.edu/SOA: The TCP connection was refused (ECONNREFUSED). (2a02:e980:4::57, 2a02:e980:5::8, 2a02:e980:6::7c, TCP_-_EDNS0_4096_D)
Warnings (4)
  • rutgers.edu/A: The server responded with no OPT record, rather than with RCODE FORMERR. (2a02:e980:6::7c, UDP_-_EDNS0_4096_D)
  • rutgers.edu/MX: The server responded with no OPT record, rather than with RCODE FORMERR. (192.230.122.8, 2a02:e980:4::57, 2a02:e980:6::7c, UDP_-_EDNS0_4096_D, UDP_-_EDNS0_512_D)
  • rutgers.edu/SOA: The server responded with no OPT record, rather than with RCODE FORMERR. (192.230.123.124, UDP_-_EDNS0_4096_D)
  • rutgers.edu/TXT: The server responded with no OPT record, rather than with RCODE FORMERR. (192.230.123.124, UDP_-_EDNS0_4096_D)

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