View on GitHub

DNSViz: A DNS visualization tool

pidforum.org

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

RRset statusRRset status

Bogus (3)
  • pidforum.org/A
  • pidforum.org/NS
  • pidforum.org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • pidforum.org/DNSKEY (alg 13, id 2371)
  • pidforum.org/DNSKEY (alg 13, id 34505)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 39681)
  • org/DNSKEY (alg 8, id 6555)
  • org/DS (alg 8, id 26974)
  • pidforum.org/DS (alg 8, id 30311)
Non_existent (1)
  • pidforum.org/DNSKEY (alg 8, id 30311)

Delegation statusDelegation status

Bogus (1)
  • org to pidforum.org
Secure (1)
  • . to org

NoticesNotices

Errors (14)
  • org to pidforum.org: 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. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • org to pidforum.org: 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. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • pidforum.org/A: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, UDP_-_EDNS0_4096_D_KN)
  • pidforum.org/DNSKEY (alg 13, id 2371): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • pidforum.org/DNSKEY (alg 13, id 34505): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • pidforum.org/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, UDP_-_EDNS0_4096_D_KN)
  • pidforum.org/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.193.129, 108.162.194.44, 162.159.38.44, 172.64.33.129, 172.64.34.44, 173.245.59.129, 2606:4700:50::a29f:262c, 2606:4700:58::adf5:3b81, 2803:f800:50::6ca2:c181, 2803:f800:50::6ca2:c22c, 2a06:98c1:50::ac40:2181, 2a06:98c1:50::ac40:222c, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • pidforum.org/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • pidforum.org/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • pidforum.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • pidforum.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • pidforum.org/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • e736fbsglt.pidforum.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • pidforum.org/TXT has errors; 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