umbc.edu
Updated:
2023-07-23 01:29:50 UTC (490 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- umbc.edu/A
- umbc.edu/NS
- umbc.edu/SOA
DNSKEY/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 status
Bogus (1)
- edu to umbc.edu
Secure (1)
- . to edu
Notices
Errors (14)
- 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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- 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). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (130.85.1.9, UDP_-_NOEDNS_)
- umbc.edu/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (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). See RFC 1035, Sec. 4.2. (130.85.1.6, 130.85.1.9, 130.85.1.11, 2620:0:5301:2::2:2, UDP_-_NOEDNS_)
- vlhr3xo4ae.umbc.edu/A 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.
- umbc.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- 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/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.
- edu to umbc.edu: A glue records exist for dnsexternal1.umbc.edu, but there are no corresponding authoritative A 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.
- 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. See RFC 6891, Sec. 6.2.6. (130.85.1.6, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
