jten.mil
Updated:
2021-08-07 05:30:02 UTC (1233 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- jten.mil/A
- jten.mil/MX
- jten.mil/NS
- jten.mil/NSEC3PARAM
- jten.mil/SOA
- jten.mil/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- jten.mil/DS (alg 7, id 14760)
- mil/DNSKEY (alg 8, id 46443)
- 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)
- jten.mil/DNSKEY (alg 7, id 14760)
- jten.mil/DNSKEY (alg 7, id 50423)
- jten.mil/DNSKEY (alg 7, id 62312)
Delegation status
Bogus (1)
- mil to jten.mil
Secure (1)
- . to mil
Notices
Errors (8)
- jten.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.112.137.170)
- jten.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.112.137.170, 199.112.138.170, UDP_-_EDNS0_4096_D_KN)
- jten.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.112.137.170, TCP_-_EDNS0_4096_D_N)
- mil to jten.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.
- jten.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 78310h94pc.jten.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- jten.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- jten.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
- RRSIG jten.mil/A alg 7, id 50423: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/A alg 7, id 62312: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/MX alg 7, id 50423: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/MX alg 7, id 62312: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/NS alg 7, id 50423: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/NS alg 7, id 62312: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/NSEC3PARAM alg 7, id 50423: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/NSEC3PARAM alg 7, id 62312: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/SOA alg 7, id 50423: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/SOA alg 7, id 62312: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/TXT alg 7, id 50423: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG jten.mil/TXT alg 7, id 62312: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- jten.mil/DS (alg 7, id 14760): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jten.mil/DS (alg 7, id 14760): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jten.mil/DS (alg 7, id 14760): 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.
- jten.mil/DS (alg 7, id 14760): 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.
- jten.mil/DS (alg 7, id 14760): 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. (199.252.154.234, UDP_-_EDNS0_4096_D_KN)
- jten.mil/DS (alg 7, id 14760): 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. (199.252.154.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.
- jten.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- jten.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- jten.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
