uscg.mil
Updated:
2021-08-08 19:12:19 UTC (1232 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (7)
- uscg.mil/A
- uscg.mil/MX
- uscg.mil/NS
- uscg.mil/NSEC3PARAM
- uscg.mil/SOA
- uscg.mil/SOA
- uscg.mil/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- 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)
- uscg.mil/DS (alg 7, id 1920)
Non_existent (3)
- uscg.mil/DNSKEY (alg 7, id 10952)
- uscg.mil/DNSKEY (alg 7, id 1920)
- uscg.mil/DNSKEY (alg 7, id 28838)
Delegation status
Bogus (1)
- mil to uscg.mil
Secure (1)
- . to mil
Notices
Errors (9)
- mil to uscg.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.
- uscg.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.211.215.69, 199.211.216.7)
- uscg.mil/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.216.7, TCP_-_EDNS0_4096_D_KN)
- uscg.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.215.69, 199.211.218.6, UDP_-_EDNS0_4096_D_KN)
- uscg.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.211.215.69, 199.211.216.7, 199.211.218.6, TCP_-_EDNS0_4096_D_N)
- uscg.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 81v47ozblx.uscg.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- uscg.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- uscg.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 26838): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- RRSIG uscg.mil/A alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/A alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/MX alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/MX alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/NS alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/NS alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/NSEC3PARAM alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/NSEC3PARAM alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/SOA alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/SOA alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/SOA alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/SOA alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/TXT alg 7, id 10952: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.mil/TXT alg 7, id 28838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- 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.
- uscg.mil/SOA: 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.211.218.6, UDP_-_EDNS0_4096_D_KN)
- uscg.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- uscg.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
