dcma.mil
Updated:
2021-05-20 21:56:13 UTC (1336 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- dcma.mil/MX
- dcma.mil/NS
- dcma.mil/SOA
- dcma.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- dcma.mil/DNSKEY (alg 8, id 26535)
- dcma.mil/DNSKEY (alg 8, id 48051)
- dcma.mil/DNSKEY (alg 8, id 64060)
- dcma.mil/DS (alg 8, id 64060)
- dcma.mil/DS (alg 8, id 64060)
- mil/DNSKEY (alg 8, id 16560)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 61794)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
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.
- rmza0bxnc1.dcma.mil/A 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 (18)
- dcma.mil/DNSKEY: The Authoritative Answer (AA) flag was set in the referral response. See RFC 1035, Sec. 4.1.1. (199.252.162.234, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- 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/MX: The Authoritative Answer (AA) flag was set in the referral response. See RFC 1035, Sec. 4.1.1. (199.252.162.234, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- dcma.mil/NS: The Authoritative Answer (AA) flag was set in the referral response. See RFC 1035, Sec. 4.1.1. (199.252.162.234, UDP_-_EDNS0_4096_D_KN)
- dcma.mil/SOA: The Authoritative Answer (AA) flag was set in the referral response. See RFC 1035, Sec. 4.1.1. (199.252.162.234, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- dcma.mil/TXT: The Authoritative Answer (AA) flag was set in the referral response. See RFC 1035, Sec. 4.1.1. (199.252.162.234, 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.
- dcma.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- rmza0bxnc1.dcma.mil/A 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/DNSKEY 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.
