View on GitHub

DNSViz: A DNS visualization tool

fj

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (1)
  • fj/SOA
Secure (3)
  • fj/NS
  • fj/NSEC3PARAM
  • fj/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • fj/DNSKEY (alg 8, id 27739)
  • fj/DNSKEY (alg 8, id 62988)
  • fj/DS (alg 8, id 27739)

Delegation statusDelegation status

Secure (1)
  • . to fj

NoticesNotices

Errors (15)
  • . 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, 2001:500:14:6138:ad::1, UDP_-_EDNS0_4096_D_KN)
  • RRSIG fj/DNSKEY alg 8, id 27739: The Signature Expiration field of the RRSIG RR (2023-04-04 23:34:26+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG fj/DNSKEY alg 8, id 27739: The Signature Expiration field of the RRSIG RR (2023-04-04 23:34:26+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG fj/NS alg 8, id 62988: The Signature Expiration field of the RRSIG RR (2023-04-03 01:23:31+00:00) is 7 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG fj/NSEC3PARAM alg 8, id 62988: The Signature Expiration field of the RRSIG RR (2023-04-02 12:26:09+00:00) is 8 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG fj/SOA alg 8, id 62988: The Signature Expiration field of the RRSIG RR (2023-04-09 15:41:27+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • fj/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, UDP_-_NOEDNS_)
  • fj/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (185.28.194.194, 185.38.108.108, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • fj/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (185.28.194.194, TCP_-_NOEDNS_)
  • fj/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • fj/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (185.28.194.194, 185.38.108.108, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • fj/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (185.28.194.194, TCP_-_EDNS0_4096_D_N)
  • fj/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • fj/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 91vjn2w7o5.fj/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • 91vjn2w7o5.fj/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fj/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph