northcom.mil
Updated:
2024-04-21 18:46:30 UTC (179 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- northcom.mil/NS
- northcom.mil/SOA
- northcom.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 25501)
- mil/DNSKEY (alg 8, id 45154)
- mil/DS (alg 8, id 16801)
- northcom.mil/DNSKEY (alg 8, id 22896)
- northcom.mil/DNSKEY (alg 8, id 28489)
- northcom.mil/DS (alg 8, id 28489)
- northcom.mil/DS (alg 8, id 28489)
- northcom.mil/DS (alg 8, id 61714)
Non_existent (1)
- northcom.mil/DNSKEY (alg 8, id 61714)
Delegation status
Secure (2)
- . to mil
- mil to northcom.mil
Notices
Errors (9)
- mil to northcom.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. (164.236.0.19, 164.236.0.20, 164.236.160.19, 164.236.160.20, UDP_-_EDNS0_4096_D_KN)
- mil to northcom.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. (164.236.0.19, 164.236.0.20, 164.236.160.19, 164.236.160.20, UDP_-_EDNS0_4096_D_KN)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:120:c:162::234, 2608:140:c:157::234, 2608:4163:1:143::234, 2608:c144:1:155::234, 2608:c184:1:180::234)
- northcom.mil/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (164.236.0.19, 164.236.0.20, 164.236.160.19, 164.236.160.20, UDP_-_NOEDNS_)
- northcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 5bpo6h8gmk.northcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- northcom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- northcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- northcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- northcom.mil/DS (alg 8, id 28489): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- northcom.mil/DS (alg 8, id 28489): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- northcom.mil/DS (alg 8, id 28489): 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.
- northcom.mil/DS (alg 8, id 28489): 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.
- northcom.mil/DS (alg 8, id 61714): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- northcom.mil/DS (alg 8, id 61714): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- northcom.mil/DS (alg 8, id 61714): 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.
- northcom.mil/DS (alg 8, id 61714): 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.
- northcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 5bpo6h8gmk.northcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- northcom.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- northcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- northcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
