dcmsa.mil
Updated:
2020-10-24 21:15:17 UTC (1519 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- dcmsa.mil/A
- dcmsa.mil/NS
- dcmsa.mil/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- dcmsa.mil/DS (alg 8, id 47665)
- mil/DNSKEY (alg 8, id 11451)
- mil/DNSKEY (alg 8, id 3870)
- mil/DNSKEY (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Non_existent (1)
- dcmsa.mil/DNSKEY (alg 8, id 47665)
Delegation status
Bogus (1)
- mil to dcmsa.mil
Secure (1)
- . to mil
Notices
Errors (18)
- dcmsa.mil zone: The following NS name(s) did not resolve to address(es): dcmsadc01.dcmsa.mil, dcmsans02.dcmsa.mil
- dcmsa.mil zone: There was an error resolving the following NS name(s) to address(es): dcmsa-dc01.dcmsa.mil, dcmsa-dc02.dcmsa.mil
- dcmsa.mil/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.37.136.48, 214.37.136.50, UDP_-_EDNS0_4096_D_K)
- dcmsa.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.37.136.48, 214.37.136.50, UDP_-_EDNS0_4096_D_K)
- dcmsa.mil/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (214.37.136.48, TCP_-_NOEDNS_)
- dcmsa.mil/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (214.37.136.48, UDP_-_NOEDNS_)
- dcmsa.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.37.136.48, 214.37.136.50, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- dcmsa.mil/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. (214.37.136.48, UDP_-_EDNS0_4096_D_K)
- dcmsa.mil/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (214.37.136.48, UDP_-_EDNS0_4096_D_K)
- dcmsa.mil/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (214.37.136.48, TCP_-_EDNS0_4096_D)
- mil to dcmsa.mil: 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. (214.37.136.48, 214.37.136.50, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- mil to dcmsa.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.37.136.48, 214.37.136.50, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- yc3qbhf45z.dcmsa.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dcmsa.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- dcmsa.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- dcmsa.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dcmsa.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- dcmsa.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- dcmsa.mil/DS (alg 8, id 47665): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dcmsa.mil/DS (alg 8, id 47665): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil to dcmsa.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): dcmsa-dc02.dcmsa.mil, dcmsa-dc01.dcmsa.mil See RFC 1034, Sec. 4.2.2.
- mil to dcmsa.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: dcmsadc01.dcmsa.mil, dcmsans02.dcmsa.mil See RFC 1034, Sec. 4.2.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- mil/DS (alg 8, id 51349): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
