usm.edu
Updated:
2022-10-13 22:11:49 UTC (773 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (8)
- usm.edu/A
- usm.edu/A (NODATA)
- usm.edu/MX
- usm.edu/MX (NODATA)
- usm.edu/NS
- usm.edu/SOA
- usm.edu/TXT
- usm.edu/TXT (NODATA)
Secure (2)
- edu/SOA
- edu/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of usm.edu/DS
- edu/DNSKEY (alg 8, id 18290)
- edu/DNSKEY (alg 8, id 28065)
- edu/DNSKEY (alg 8, id 28775)
- edu/DS (alg 8, id 28065)
Delegation status
Insecure (1)
- edu to usm.edu
Secure (1)
- . to edu
Notices
Errors (17)
- usm.edu zone: The following NS name(s) did not resolve to address(es): darbanazure, dns_azure_internal
- usm.edu zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (131.95.186.31)
- usm.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (64.57.246.82)
- usm.edu/A (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (131.95.186.31, UDP_-_EDNS0_4096_D_KN)
- usm.edu/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (131.95.186.31, UDP_-_EDNS0_4096_D_KN)
- usm.edu/MX (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (131.95.186.31, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- usm.edu/MX (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (131.95.186.31, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- usm.edu/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (131.95.186.31, UDP_-_EDNS0_4096_D_KN)
- usm.edu/SOA: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (131.95.186.31, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- usm.edu/SOA: The server was not reachable over TCP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (64.57.246.82, TCP_-_EDNS0_4096_D_N)
- usm.edu/TXT (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (131.95.186.31, UDP_-_EDNS0_4096_D_KN)
- usm.edu/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (131.95.186.31, UDP_-_EDNS0_4096_D_KN)
- r29afo0kds.usm.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
- usm.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- usm.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- usm.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- usm.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- edu to usm.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): darban3.cc.usm.edu, darban4.cc.usm.edu, darbanazure, dns_azure_internal See RFC 1034, Sec. 4.2.2.
- edu to usm.edu: The following NS name(s) were found in the delegation NS RRset (i.e., in the edu zone), but not in the authoritative NS RRset: darban5.usm.edu, ns2.usm.edu See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
