View on GitHub

DNSViz: A DNS visualization tool

weber.edu

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

RRset statusRRset status

Bogus (6)
  • weber.edu/A
  • weber.edu/AAAA
  • weber.edu/MX
  • weber.edu/NS
  • weber.edu/NSEC3PARAM
  • weber.edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 30503)
  • edu/DS (alg 8, id 28065)
  • weber.edu/DS (alg 10, id 831)
  • weber.edu/DS (alg 8, id 29629)
  • weber.edu/DS (alg 8, id 62605)
Non_existent (4)
  • weber.edu/DNSKEY (alg 10, id 831)
  • weber.edu/DNSKEY (alg 8, id 10440)
  • weber.edu/DNSKEY (alg 8, id 29629)
  • weber.edu/DNSKEY (alg 8, id 62605)

Delegation statusDelegation status

Bogus (1)
  • edu to weber.edu
Secure (1)
  • . to edu

NoticesNotices

Errors (32)
  • edu to weber.edu: 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.
  • weber.edu zone: The server(s) were not responsive to queries over TCP. (137.190.2.8, 137.190.225.8, 205.120.163.7, 2001:1948:214:225::8, 2001:1948:218:10::7)
  • weber.edu/A: No response was received from the server over TCP (tried 4 times). (205.120.163.7, TCP_-_EDNS0_4096_D)
  • weber.edu/A: No response was received from the server over UDP (tried 12 times). (2001:1948:214:225::8, UDP_-_NOEDNS_)
  • weber.edu/AAAA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. (137.190.2.8, UDP_-_EDNS0_4096_)
  • weber.edu/AAAA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. (137.190.225.8, UDP_-_NOEDNS_)
  • weber.edu/AAAA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). (137.190.2.8, UDP_-_EDNS0_4096_D_KN)
  • weber.edu/AAAA: 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). (137.190.225.8, UDP_-_EDNS0_4096_D_KN)
  • weber.edu/AAAA: No response was received from the server over UDP (tried 12 times). (205.120.163.7, UDP_-_NOEDNS_)
  • weber.edu/AAAA: The DNSSEC records necessary to validate the response could not be retrieved from the server. (137.190.2.8, 137.190.225.8, UDP_-_EDNS0_4096_D_KN)
  • weber.edu/DNSKEY: No response was received from the server over TCP (tried 10 times). (137.190.225.8, TCP_-_EDNS0_4096_D_N)
  • weber.edu/DNSKEY: No response was received from the server over TCP (tried 9 times). (137.190.2.8, TCP_-_EDNS0_4096_D)
  • weber.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). (205.120.163.7, 2001:1948:214:225::8, 2001:1948:218:10::7, UDP_-_EDNS0_4096_D_KN, UDP_-_NOEDNS_)
  • weber.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). (137.190.2.8, 137.190.225.8, 205.120.163.7, UDP_-_EDNS0_512_D_KN)
  • weber.edu/MX: No response was received from the server over TCP (tried 6 times). (205.120.163.7, TCP_-_EDNS0_4096_)
  • weber.edu/MX: No response was received from the server over UDP (tried 12 times). (137.190.2.8, UDP_-_NOEDNS_)
  • weber.edu/MX: No response was received from the server over UDP (tried 4 times). (137.190.225.8, 205.120.163.7, 2001:1948:214:225::8, UDP_-_EDNS0_512_D_KN)
  • weber.edu/NS: No response was received from the server over TCP (tried 4 times). (2001:1948:214:225::8, TCP_-_EDNS0_4096_D)
  • weber.edu/NS: No response was received from the server over TCP (tried 5 times). (205.120.163.7, TCP_-_EDNS0_4096_D_KN)
  • weber.edu/NSEC3PARAM: No response was received from the server over TCP (tried 4 times). (205.120.163.7, TCP_-_EDNS0_4096_D)
  • weber.edu/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). (137.190.2.8, 2001:1948:214:225::8, UDP_-_NOEDNS_)
  • weber.edu/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. (205.120.163.7, UDP_-_EDNS0_4096__0x20)
  • weber.edu/SOA: No response was received from the server over TCP (tried 3 times). (137.190.2.8, 137.190.225.8, 205.120.163.7, 2001:1948:214:225::8, 2001:1948:218:10::7, TCP_-_EDNS0_4096_D_N)
  • weber.edu/SOA: No response was received from the server over TCP (tried 4 times). (137.190.2.8, 2001:1948:214:225::8, TCP_-_EDNS0_4096_D, TCP_-_EDNS0_4096_D_0x20)
  • weber.edu/SOA: No response was received from the server over TCP (tried 5 times). (137.190.2.8, 137.190.225.8, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_N)
  • weber.edu/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). (205.120.163.7, UDP_-_EDNS0_4096_D_KN_0x20)
  • weber.edu/SOA: No response was received from the server over UDP (tried 12 times). (2001:1948:214:225::8, UDP_-_NOEDNS_)
  • weber.edu/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. (205.120.163.7, UDP_-_EDNS0_4096_D_KN_0x20)
  • weber.edu/TXT: No response was received from the server over TCP (tried 12 times). (137.190.2.8, 2001:1948:218:10::7, TCP_-_EDNS0_4096_D_KN)
  • weber.edu/TXT: No response was received from the server over TCP (tried 3 times). (137.190.225.8, TCP_-_EDNS0_4096_)
  • weber.edu/TXT: No response was received from the server over TCP (tried 7 times). (2001:1948:214:225::8, TCP_-_EDNS0_4096_D_KN)
  • weber.edu/TXT: No response was received from the server over UDP (tried 12 times). (205.120.163.7, UDP_-_NOEDNS_)
Warnings (11)
  • RRSIG weber.edu/A alg 10, id 831: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG weber.edu/AAAA alg 10, id 831: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG weber.edu/MX alg 10, id 831: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG weber.edu/NS alg 10, id 831: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG weber.edu/NSEC3PARAM alg 10, id 831: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG weber.edu/SOA alg 10, id 831: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • edu to weber.edu: Authoritative AAAA records exist for dns8.weber.edu, but there are no corresponding AAAA glue records.
  • weber.edu/DS (alg 8, id 62605): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • weber.edu/DS (alg 8, id 62605): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • weber.edu/DS (alg 8, id 62605): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • weber.edu/DS (alg 8, id 62605): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.

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