umbc.edu
Updated:
2020-07-24 16:38:51 UTC (1582 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- umbc.edu/A
- umbc.edu/MX
- umbc.edu/NS
- umbc.edu/SOA
- umbc.edu/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- edu/DNSKEY (alg 8, id 28065)
- edu/DNSKEY (alg 8, id 33233)
- edu/DS (alg 8, id 28065)
- 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 (15)
- umbc.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:0:5301:2::2:2, 2620:0:5301:2::2:3)
- umbc.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:5301:2::2:2, 2620:0:5301:2::2:3, UDP_-_NOEDNS_)
- umbc.edu/MX: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (130.85.1.6, UDP_-_EDNS0_4096_)
- umbc.edu/MX: 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). See RFC 6891, Sec. 6.1.4. (130.85.1.6, UDP_-_EDNS0_4096_D_K)
- umbc.edu/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (130.85.1.6, UDP_-_EDNS0_512_D_K)
- umbc.edu/MX: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (130.85.1.6, UDP_-_EDNS0_4096_D_K)
- umbc.edu/NS: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (130.85.1.6, UDP_-_EDNS0_4096_)
- umbc.edu/NS: 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). See RFC 6891, Sec. 6.1.4. (130.85.1.6, UDP_-_EDNS0_4096_D_K)
- umbc.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:5301:2::2:2, 2620:0:5301:2::2:3, UDP_-_NOEDNS_)
- umbc.edu/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (130.85.1.6, UDP_-_EDNS0_4096_D_K)
- umbc.edu/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (130.85.1.6, UDP_-_EDNS0_4096_)
- umbc.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). See RFC 6891, Sec. 6.1.4. (130.85.1.6, UDP_-_EDNS0_4096_D_K)
- umbc.edu/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (130.85.1.6, UDP_-_EDNS0_4096_D_K)
- umbc.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- umbc.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
- 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/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/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (130.85.1.6, UDP_-_EDNS0_4096_D_K_0x20)
- umbc.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- w3qi5batnf.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.
- umbc.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
