uscg.gov

Updated: 2021-05-17 16:52:58 UTC (1289 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (3)

uscg.gov/NS
uscg.gov/SOA
uscg.gov/TXT

DNSKEY/DS/NSEC status

Bogus (1)

uscg.gov/DNSKEY (alg 7, id 32207)

Secure (13)

./DNSKEY (alg 8, id 14631)
./DNSKEY (alg 8, id 20326)
gov/DNSKEY (alg 8, id 48498)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
uscg.gov/DNSKEY (alg 7, id 32270)
uscg.gov/DNSKEY (alg 7, id 32582)
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)

Non_existent (1)

uscg.gov/DNSKEY (alg 7, id 32582)

Delegation status

Secure (2)

. to gov
gov to uscg.gov

Notices

Errors (25)

RRSIG uscg.gov/DNSKEY alg 7, id 32270: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 32270: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 32270: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 32270: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 64494: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 64494: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 64494: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 64494: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 8508: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 8508: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 8508: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG uscg.gov/DNSKEY alg 7, id 8508: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
gov to uscg.gov: 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. (152.121.33.3, TCP_-_EDNS0_4096_D_KN)
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 (alg 7, id 32582): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (152.121.33.3, TCP_-_EDNS0_4096_D_KN)
uscg.gov/DNSKEY: No response was received from the server over TCP (tried 11 times). See RFC 1035, Sec. 4.2. (152.121.50.3, TCP_-_EDNS0_4096_D_KN)
uscg.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (152.121.33.3, UDP_-_EDNS0_512_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.50.3, TCP_-_EDNS0_4096_D_N)
uscg.gov/TXT: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (152.121.33.3, TCP_-_EDNS0_4096_D_KN)
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.
xpfltgcqnb.uscg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (53)

RRSIG uscg.gov/DNSKEY alg 7, id 32270: 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 32270: 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 32270: 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 32270: 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 32270: 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 32270: 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 32270: 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 32270: 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 32582: 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 32582: 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 32582: 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 32582: 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 32582: 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 32582: 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 32582: 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 32582: 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 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 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/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/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 32270: 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 32582: 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 32270: 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 32582: 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 32270: 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 32582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
uscg.gov/DNSKEY (alg 7, id 32207): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (152.121.2.19, TCP_-_EDNS0_4096_D_KN)
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/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (152.121.33.3, UDP_-_EDNS0_4096_D_KN)
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.
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.