umbc.edu
Updated:
2024-08-05 18:46:13 UTC (108 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- umbc.edu/A
- umbc.edu/AAAA
- umbc.edu/MX
- umbc.edu/NS
- umbc.edu/SOA
- umbc.edu/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- edu/DNSKEY (alg 13, id 30299)
- edu/DNSKEY (alg 13, id 35663)
- 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 status
Secure (2)
- . to edu
- edu to umbc.edu
Notices
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 (19)
- RRSIG umbc.edu/A alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/AAAA alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/DNSKEY alg 5, id 62866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/DNSKEY alg 5, id 62866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/DNSKEY alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/DNSKEY alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/MX alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/NS alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/SOA alg 5, id 645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG umbc.edu/TXT alg 5, id 645: DNSSEC implementers are recommended against implementing 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/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- umbc.edu/CDNSKEY 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.
- umbc.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- wj2se.aqh3f.umbc.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- umbc.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
