uscg.gov
Updated:
2021-08-18 17:08:43 UTC (1195 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- uscg.gov/NS
- uscg.gov/NSEC3PARAM
- uscg.gov/SOA
- uscg.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- uscg.gov/DNSKEY (alg 7, id 24980)
- uscg.gov/DNSKEY (alg 7, id 64494)
- uscg.gov/DNSKEY (alg 7, id 8508)
- uscg.gov/DS (alg 7, id 64494)
- uscg.gov/DS (alg 7, id 64494)
- uscg.gov/DS (alg 7, id 8508)
- uscg.gov/DS (alg 7, id 8508)
Delegation status
Secure (2)
- . to gov
- gov to uscg.gov
Notices
Errors (11)
- uscg.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (152.121.2.19)
- uscg.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (152.121.50.3)
- uscg.gov/DNSKEY: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (152.121.2.19, TCP_-_EDNS0_4096_D_KN)
- uscg.gov/DNSKEY: No response was received from the server over TCP (tried 9 times). See RFC 1035, Sec. 4.2. (152.121.50.3, TCP_-_EDNS0_4096_D_KN)
- uscg.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (152.121.2.19, 152.121.33.3, 152.121.50.3, TCP_-_EDNS0_4096_D_N)
- uscg.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- vzun31qcj8.uscg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (27)
- RRSIG uscg.gov/DNSKEY alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 64494: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 64494: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 64494: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 8508: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 8508: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/DNSKEY alg 7, id 8508: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/NS alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/NSEC3PARAM alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/SOA alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG uscg.gov/TXT alg 7, id 24980: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- uscg.gov/DS (alg 7, id 64494): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- uscg.gov/DS (alg 7, id 64494): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- uscg.gov/DS (alg 7, id 64494): 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.gov/DS (alg 7, id 64494): 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.gov/DS (alg 7, id 8508): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- uscg.gov/DS (alg 7, id 8508): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- uscg.gov/DS (alg 7, id 8508): 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.gov/DS (alg 7, id 8508): 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.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- uscg.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- vzun31qcj8.uscg.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
