fj
Updated:
2022-03-08 06:05:53 UTC (992 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- fj/NS
- fj/NSEC3PARAM
- fj/SOA
DNSKEY/DS/NSEC status
Bogus (2)
- fj/DNSKEY (alg 8, id 12931)
- fj/DNSKEY (alg 8, id 24459)
Secure (3)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- fj/DS (alg 8, id 18952)
Non_existent (1)
- fj/DNSKEY (alg 8, id 18952)
Delegation status
Bogus (1)
- . to fj
Notices
Errors (18)
- . to fj: 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. (185.28.194.194, 185.38.108.108, 204.61.216.138, UDP_-_EDNS0_4096_D_KN)
- . to fj: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.28.194.194, 185.38.108.108, 204.61.216.138, UDP_-_EDNS0_4096_D_KN)
- fj zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2402:2940:100:100d::1)
- fj zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (144.120.146.65)
- fj zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (144.120.146.1)
- fj/DNSKEY: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2402:2940:100:100c::1, TCP_-_EDNS0_4096_D)
- fj/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.120.146.65, UDP_-_NOEDNS_)
- fj/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (144.120.146.65, 2402:2940:100:100c::1, 2402:2940:100:100d::1, UDP_-_EDNS0_512_D_KN)
- fj/DNSKEY: No response was received from the server over UDP (tried 7 times). See RFC 1035, Sec. 4.2. (2402:2940:100:100d::1, UDP_-_EDNS0_4096_D)
- fj/NS: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (144.120.146.65, UDP_-_EDNS0_4096_)
- fj/NS: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared. See RFC 6891, Sec. 6.1.4. (144.120.146.65, UDP_-_EDNS0_4096_D_KN)
- fj/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.120.146.1, UDP_-_NOEDNS_)
- fj/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.120.146.65, UDP_-_NOEDNS_)
- fj/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (144.120.146.65, 2402:2940:100:100c::1, 2402:2940:100:100d::1, TCP_-_EDNS0_4096_D_N)
- fj/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.120.146.65, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- fj/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- fj/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ty8p2odfj5.fj/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- fj/NS: 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. (2402:2940:100:100d::1, UDP_-_EDNS0_4096_D_KN)
- fj/NSEC3PARAM: 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. (2402:2940:100:100d::1, UDP_-_EDNS0_4096_D_KN)
- fj/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ty8p2odfj5.fj/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
