cftc.gov
Updated:
2023-04-05 12:57:53 UTC (598 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- cftc.gov/A
- cftc.gov/MX
- cftc.gov/NS
- cftc.gov/NSEC3PARAM
- cftc.gov/SOA
- cftc.gov/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- cftc.gov/DS (alg 7, id 49003)
- cftc.gov/DS (alg 7, id 51084)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (3)
- cftc.gov/DNSKEY (alg 7, id 49003)
- cftc.gov/DNSKEY (alg 7, id 51084)
- cftc.gov/DNSKEY (alg 7, id 62310)
Delegation status
Bogus (1)
- gov to cftc.gov
Secure (1)
- . to gov
Notices
Errors (8)
- cftc.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (198.6.1.18, 198.6.1.19)
- cftc.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (198.6.1.18, 198.6.1.19, UDP_-_EDNS0_4096_D_KN)
- cftc.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (198.6.1.18, 198.6.1.19, TCP_-_EDNS0_4096_D_N)
- gov to cftc.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.
- cftc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 89qtkhypxz.cftc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- cftc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- cftc.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- RRSIG cftc.gov/A alg 7, id 62310: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG cftc.gov/MX alg 7, id 62310: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG cftc.gov/NS alg 7, id 62310: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG cftc.gov/NSEC3PARAM alg 7, id 62310: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG cftc.gov/SOA alg 7, id 62310: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG cftc.gov/TXT alg 7, id 62310: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- cftc.gov/DS (alg 7, id 49003): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cftc.gov/DS (alg 7, id 49003): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- cftc.gov/DS (alg 7, id 49003): 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.
- cftc.gov/DS (alg 7, id 49003): 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.
- cftc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- cftc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
