dcma.mil
Updated:
2021-08-16 16:04:57 UTC (1245 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- dcma.mil/MX
- dcma.mil/NS
- dcma.mil/NSEC3PARAM
- dcma.mil/NSEC3PARAM
- dcma.mil/SOA
- dcma.mil/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- dcma.mil/DS (alg 8, id 64060)
- mil/DNSKEY (alg 8, id 39879)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 9498)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Non_existent (3)
- dcma.mil/DNSKEY (alg 8, id 17688)
- dcma.mil/DNSKEY (alg 8, id 37311)
- dcma.mil/DNSKEY (alg 8, id 64060)
Delegation status
Bogus (1)
- mil to dcma.mil
Secure (1)
- . to mil
Notices
Errors (9)
- dcma.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (144.183.130.117)
- dcma.mil/A: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (144.183.129.10, 144.183.130.117, TCP_-_EDNS0_4096_D_KN)
- dcma.mil/AAAA: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (144.183.129.10, 144.183.130.117, TCP_-_EDNS0_4096_D_KN)
- dcma.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.183.129.10, 144.183.130.117, UDP_-_EDNS0_4096_D_KN)
- dcma.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (144.183.129.10, 144.183.130.117, TCP_-_EDNS0_4096_D_N)
- mil to dcma.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.
- dcma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- ojf86ba4si.dcma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 17688: The value of the Signature Inception field of the RRSIG RR (2021-08-16 16:04:40+00:00) is within possible clock skew range (17 seconds) of the current time (2021-08-16 16:04:57+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 17688: The value of the Signature Inception field of the RRSIG RR (2021-08-16 16:04:45+00:00) is within possible clock skew range (12 seconds) of the current time (2021-08-16 16:04:57+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 37311: The value of the Signature Inception field of the RRSIG RR (2021-08-16 16:04:40+00:00) is within possible clock skew range (17 seconds) of the current time (2021-08-16 16:04:57+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 37311: The value of the Signature Inception field of the RRSIG RR (2021-08-16 16:04:45+00:00) is within possible clock skew range (12 seconds) of the current time (2021-08-16 16:04:57+00:00). See RFC 4035, Sec. 5.3.1.
- dcma.mil/DS (alg 8, id 64060): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dcma.mil/DS (alg 8, id 64060): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dcma.mil/DS (alg 8, id 64060): 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.
- dcma.mil/DS (alg 8, id 64060): 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.
- dcma.mil/SOA: 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. (144.183.129.10, UDP_-_EDNS0_4096_D_KN)
- 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.
