dren.net
Updated:
2023-12-05 15:41:50 UTC (381 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- dren.net/MX
- dren.net/NS
- dren.net/SOA
- dren.net/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- dren.net/DNSKEY (alg 13, id 18414)
- dren.net/DNSKEY (alg 13, id 36368)
- dren.net/DS (alg 13, id 36368)
- net/DNSKEY (alg 13, id 37331)
- net/DNSKEY (alg 13, id 44222)
- net/DS (alg 13, id 37331)
Delegation status
Secure (2)
- . to net
- net to dren.net
Notices
Errors (4)
- dren.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.32.59.226, 140.32.61.226)
- dren.net zone: There was an error resolving the following NS name(s) to address(es): auth-apg.dren.mil, auth-sandiego.dren.mil, auth-wpafb.dren.mil
- dren.net/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.59.226, 140.32.61.226, UDP_-_NOEDNS_)
- dren.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- net to dren.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): auth-apg.dren.mil, auth-sandiego.dren.mil, auth-wpafb.dren.mil See RFC 1034, Sec. 4.2.2.
- net to dren.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: auth-east.dren.mil, auth-west.dren.mil, ns1.arl.hpc.mil See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
