dcma.mil
Updated:
2023-08-16 20:07:05 UTC (493 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 (12)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- dcma.mil/DNSKEY (alg 8, id 29508)
- dcma.mil/DNSKEY (alg 8, id 39843)
- dcma.mil/DNSKEY (alg 8, id 41560)
- dcma.mil/DNSKEY (alg 8, id 54637)
- dcma.mil/DS (alg 8, id 41560)
- dcma.mil/DS (alg 8, id 41560)
- mil/DNSKEY (alg 8, id 14098)
- mil/DNSKEY (alg 8, id 26446)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
Delegation status
Secure (2)
- . to mil
- mil to dcma.mil
Notices
Errors (4)
- 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.
- 5l2qkjw736.dcma.mil/A 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 (15)
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 29508: The value of the Signature Inception field of the RRSIG RR (2023-08-16 20:07:05+00:00) is within possible clock skew range (0 seconds) of the current time (2023-08-16 20:07:05+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 29508: The value of the Signature Inception field of the RRSIG RR (2023-08-16 20:07:05+00:00) is within possible clock skew range (0 seconds) of the current time (2023-08-16 20:07:05+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 39843: The value of the Signature Inception field of the RRSIG RR (2023-08-16 20:07:05+00:00) is within possible clock skew range (0 seconds) of the current time (2023-08-16 20:07:05+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG dcma.mil/NSEC3PARAM alg 8, id 39843: The value of the Signature Inception field of the RRSIG RR (2023-08-16 20:07:05+00:00) is within possible clock skew range (0 seconds) of the current time (2023-08-16 20:07:05+00:00). See RFC 4035, Sec. 5.3.1.
- dcma.mil/DS (alg 8, id 41560): 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 41560): 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 41560): 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 41560): 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 14098): 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, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 26446): 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, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 62470): 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, UDP_-_EDNS0_4096_D_KN)
- 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.
- 5l2qkjw736.dcma.mil/A 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.
