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 (3)
  • fj/NS
  • fj/NSEC3PARAM
  • fj/SOA

DNSKEY/DS/NSEC statusDNSKEY/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 statusDelegation status

Bogus (1)
  • . to fj

NoticesNotices

Errors (8)
  • . 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, 2402:2940:100:100d::1, 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, 2402:2940:100:100d::1, UDP_-_EDNS0_4096_D_KN)
  • 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_-_EDNS0_4096_D_KN)
  • fj/DNSKEY: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (144.120.146.1, 2402:2940:100:100c::1, UDP_-_EDNS0_4096_D_KN)
  • fj/DNSKEY: No response was received from the server over UDP (tried 4 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_-_EDNS0_512_D_KN)
  • 7vq4fsogwm.fj/A 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.
  • fj/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • 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. (144.120.146.1, 144.120.146.65, 2402:2940:100:100d::1, UDP_-_EDNS0_4096_D_KN)
  • fj/NSEC3PARAM: 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. (144.120.146.65, 2402:2940:100:100c::1, 2402:2940:100:100d::1, UDP_-_EDNS0_4096_D_KN)
  • fj/SOA: 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. (144.120.146.1, 144.120.146.65, 2402:2940:100:100c::1, 2402:2940:100:100d::1, UDP_-_EDNS0_4096_D_KN_0x20)
  • 7vq4fsogwm.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