fj
Updated:
2022-08-24 04:41:01 UTC (823 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- fj/NS
- fj/SOA
DNSKEY/DS/NSEC status
Secure (5)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- fj/DNSKEY (alg 8, id 12931)
- fj/DNSKEY (alg 8, id 24459)
- fj/DS (alg 8, id 12931)
Delegation status
Secure (1)
- . to fj
Notices
Errors (12)
- fj zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (204.61.216.138)
- fj zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (204.61.216.138)
- fj zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (144.120.146.1, 144.120.146.65, 2402:2940:100:100c::1, 2402:2940:100:100d::1)
- fj/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (204.61.216.138, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- fj/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.120.146.1, 144.120.146.65, 2402:2940:100:100c::1, 2402:2940:100:100d::1, UDP_-_NOEDNS_)
- fj/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (204.61.216.138, UDP_-_NOEDNS_)
- fj/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 204.61.216.138, UDP_-_NOEDNS_)
- fj/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (204.61.216.138, TCP_-_NOEDNS_)
- fj/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (204.61.216.138, 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.
- g54hjobv2d.fj/A has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
