dcma.mil
Updated:
2022-02-26 21:43:07 UTC (1044 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- dcma.mil/MX
- dcma.mil/NS
- dcma.mil/NSEC3PARAM
- dcma.mil/NSEC3PARAM
- dcma.mil/SOA
- dcma.mil/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- dcma.mil/DNSKEY (alg 8, id 63213)
- dcma.mil/DNSKEY (alg 8, id 64339)
- dcma.mil/DS (alg 8, id 64339)
- dcma.mil/DS (alg 8, id 64339)
- mil/DNSKEY (alg 8, id 25191)
- mil/DNSKEY (alg 8, id 49023)
- mil/DNSKEY (alg 8, id 56347)
- mil/DS (alg 8, id 56347)
Delegation status
Secure (2)
- . to mil
- mil to dcma.mil
Notices
Errors (5)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:c144:1:155::234)
- 2xpa8on7lv.dcma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 63213: The value of the Signature Inception field of the RRSIG RR (2022-02-26 21:43:07+00:00) is within possible clock skew range (0 seconds) of the current time (2022-02-26 21:43:07+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 63213: The value of the Signature Inception field of the RRSIG RR (2022-02-26 21:43:07+00:00) is within possible clock skew range (0 seconds) of the current time (2022-02-26 21:43:07+00:00). See RFC 4035, Sec. 5.3.1.
- dcma.mil/DS (alg 8, id 64339): 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 64339): 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 64339): 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 64339): 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/DNSKEY (alg 8, id 25191): 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. (2608:140:c:157::234, 2608:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 49023): 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. (2608:140:c:157::234, 2608:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 56347): 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. (2608:140:c:157::234, 2608:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
- 2xpa8on7lv.dcma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- dcma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
