View on GitHub

DNSViz: A DNS visualization tool

umbc.edu

Updated: 2024-05-21 13:28:31 UTC (33 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • umbc.edu/A
  • umbc.edu/AAAA
  • umbc.edu/MX
  • umbc.edu/NS
  • umbc.edu/SOA
  • umbc.edu/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DNSKEY (alg 13, id 41543)
  • edu/DS (alg 13, id 35663)
  • umbc.edu/DNSKEY (alg 5, id 62866)
  • umbc.edu/DNSKEY (alg 5, id 645)
  • umbc.edu/DS (alg 5, id 62866)

Delegation statusDelegation status

Secure (2)
  • . to edu
  • edu to umbc.edu

NoticesNotices

Errors (3)
  • umbc.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:0:5301:2::2:3)
  • umbc.edu/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (2620:0:5301:2::2:3, UDP_-_EDNS0_4096_D_KN)
  • umbc.edu/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (2620:0:5301:2::2:3, UDP_-_EDNS0_4096_D_KN)
Warnings (17)
  • RRSIG umbc.edu/A alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/AAAA alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/DNSKEY alg 5, id 62866: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/DNSKEY alg 5, id 62866: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/DNSKEY alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/DNSKEY alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/MX alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/NS alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/SOA alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG umbc.edu/TXT alg 5, id 645: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • edu to umbc.edu: Authoritative AAAA records exist for dnsexternal.umbc.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • edu to umbc.edu: Authoritative AAAA records exist for dnsexternal1.umbc.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • edu to umbc.edu: Authoritative AAAA records exist for dnsexternal2.umbc.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • umbc.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • umbc.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • b5kpxagw0l.umbc.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • umbc.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.

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