miami.edu
Updated:
2023-09-20 01:10:50 UTC (216 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- miami.edu/A
- miami.edu/MX
- miami.edu/NS
- miami.edu/SOA
- miami.edu/TXT
Secure (1)
- edu/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of miami.edu/DS
- edu/DNSKEY (alg 13, id 35663)
- edu/DNSKEY (alg 13, id 8957)
- edu/DS (alg 13, id 35663)
Non_existent (1)
- edu/DNSKEY (alg 8, id 24314)
Delegation status
Insecure (1)
- edu to miami.edu
Secure (1)
- . to edu
Notices
Errors (12)
- miami.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. (129.171.64.3)
- miami.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. (129.171.64.3)
- miami.edu zone: The server(s) were not responsive to queries over UDP. (2600:1406:32::41)
- miami.edu/A: No response was received from the server over UDP (tried 12 times). (2600:1406:32::41, UDP_-_NOEDNS_)
- miami.edu/A: The response had an invalid RCODE (REFUSED). (129.171.64.3, UDP_-_EDNS0_4096_D_KN)
- miami.edu/DNSKEY: The response had an invalid RCODE (REFUSED). (129.171.64.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- miami.edu/MX: The response had an invalid RCODE (REFUSED). (129.171.64.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- miami.edu/NS: No response was received from the server over UDP (tried 12 times). (2600:1406:32::41, UDP_-_NOEDNS_)
- miami.edu/NS: The response had an invalid RCODE (REFUSED). (129.171.64.3, UDP_-_EDNS0_4096_D_KN)
- miami.edu/SOA: The response had an invalid RCODE (REFUSED). (129.171.64.3, TCP_-_EDNS0_4096_D_N)
- miami.edu/SOA: The response had an invalid RCODE (REFUSED). (129.171.64.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- miami.edu/TXT: The response had an invalid RCODE (REFUSED). (129.171.64.3, UDP_-_EDNS0_4096_D_KN)
Warnings (1)
- edu to miami.edu: The glue address(es) for e1.miami.edu (64.56.84.250) differed from its authoritative address(es) (64.56.84.250, 129.171.64.3).
JavaScript is required to make the graph below interactive.
