View on GitHub

DNSViz: A DNS visualization tool

umbc.edu

Updated: 2023-07-23 01:29:50 UTC (272 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

Bogus (3)
  • umbc.edu/A
  • umbc.edu/NS
  • umbc.edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • edu/DNSKEY (alg 8, id 24314)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DS (alg 8, id 28065)
  • umbc.edu/DS (alg 5, id 62866)
Non_existent (2)
  • umbc.edu/DNSKEY (alg 5, id 62866)
  • umbc.edu/DNSKEY (alg 5, id 645)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • edu to umbc.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.
  • umbc.edu zone: There was an error resolving the following NS name(s) to address(es): dnsexternal.umbc.edu
  • umbc.edu/AAAA: No response was received from the server over UDP (tried 12 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_)
  • umbc.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_)
  • umbc.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_EDNS0_512_D_KN)
  • umbc.edu/MX: No response was received from the server over UDP (tried 12 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_)
  • umbc.edu/MX: No response was received from the server over UDP (tried 4 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_EDNS0_512_D_KN)
  • umbc.edu/NS: No response was received from the server over UDP (tried 12 times). (130.85.1.9, UDP_-_NOEDNS_)
  • umbc.edu/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_)
  • umbc.edu/SOA: No response was received from the server over UDP (tried 12 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • umbc.edu/TXT: No response was received from the server over UDP (tried 12 times). (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_)
Warnings (6)
  • RRSIG umbc.edu/A alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG umbc.edu/NS alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG umbc.edu/SOA alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • edu to umbc.edu: A glue records exist for dnsexternal1.umbc.edu, but there are no corresponding authoritative A records.
  • edu to umbc.edu: Authoritative AAAA records exist for dnsexternal1.umbc.edu, but there are no corresponding AAAA glue records.
  • umbc.edu/NS: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. (130.85.1.6, UDP_-_EDNS0_4096_D_KN)

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