View on GitHub

DNSViz: A DNS visualization tool

isoc.org

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

RRset statusRRset status

Bogus (5)
  • isoc.org/A
  • isoc.org/AAAA
  • isoc.org/NS
  • isoc.org/SOA
  • isoc.org/TXT
Secure (7)
  • isoc.org/A
  • isoc.org/AAAA
  • isoc.org/MX
  • isoc.org/NS
  • isoc.org/SOA
  • isoc.org/TXT
  • org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • isoc.org/DNSKEY (alg 7, id 3330)
  • isoc.org/DNSKEY (alg 7, id 38570)
Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of isoc.org/DS
  • isoc.org/DNSKEY (alg 13, id 2371)
  • isoc.org/DNSKEY (alg 13, id 34505)
  • isoc.org/DS (alg 13, id 2371)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 22064)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 63858)
  • org/DS (alg 8, id 26974)

Delegation statusDelegation status

Secure (2)
  • . to org
  • org to isoc.org

NoticesNotices

Errors (59)
  • NSEC3 proving non-existence of isoc.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of isoc.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • RRSIG isoc.org/MX alg 13, id 34505: The TTL of the RRset (3600) exceeds the value of the Original TTL field of the RRSIG RR covering it (300). See RFC 4035, Sec. 2.2.
  • isoc.org/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/A: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K)
  • isoc.org/A: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/AAAA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/AAAA: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K)
  • isoc.org/AAAA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DNSKEY (alg 13, id 2371): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DNSKEY (alg 13, id 2371): The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • isoc.org/DNSKEY (alg 13, id 34505): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DNSKEY (alg 13, id 34505): The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • isoc.org/DNSKEY (alg 7, id 3330): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DNSKEY (alg 7, id 3330): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DNSKEY (alg 7, id 38570): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • isoc.org/DNSKEY (alg 7, id 38570): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DNSKEY (alg 7, id 38570): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • isoc.org/MX: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • isoc.org/MX: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • isoc.org/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/NS: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K)
  • isoc.org/NS: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • isoc.org/SOA: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • isoc.org/SOA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • isoc.org/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/TXT: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K)
  • isoc.org/TXT: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • org to isoc.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. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • org to isoc.org: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (65.22.6.1, 65.22.6.79, 65.22.7.1, 65.22.8.1, 65.22.9.1, 185.49.140.62, 2a01:8840:6::1, 2a01:8840:7::1, 2a01:8840:8::1, 2a01:8840:9::1, 2a04:b900::8:0:0:62, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 2ecmy1wv67.isoc.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • NSEC3 proving non-existence of isoc.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of isoc.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of isoc.org/DS alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of isoc.org/DS alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/A alg 7, id 38570: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/AAAA alg 7, id 38570: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DNSKEY alg 7, id 3330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DNSKEY alg 7, id 3330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DS alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/MX alg 7, id 38570: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/NS alg 7, id 38570: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/SOA alg 7, id 38570: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/TXT alg 7, id 38570: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/SOA alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • isoc.org/DNSKEY (alg 7, id 3330): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (108.162.192.69, 108.162.195.34, 162.159.44.34, 172.64.32.69, 172.64.35.34, 173.245.58.69, 2606:4700:50::adf5:3a45, 2606:4700:58::a29f:2c22, 2803:f800:50::6ca2:c045, 2803:f800:50::6ca2:c322, 2a06:98c1:50::ac40:2045, 2a06:98c1:50::ac40:2322, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • org to isoc.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): a0.dig.afilias-nst.info, d0.dig.afilias-nst.info, b0.dig.afilias-nst.info, c0.dig.afilias-nst.info See RFC 1034, Sec. 4.2.2.
  • org to isoc.org: The following NS name(s) were found in the delegation NS RRset (i.e., in the org zone), but not in the authoritative NS RRset: ns1.ams1.afilias-nst.info See RFC 1034, Sec. 4.2.2.
  • org/DNSKEY (alg 7, id 17883): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (199.19.53.1, 199.19.56.1, 199.19.57.1, 199.249.112.1, 199.249.120.1, 2001:500:b::1, 2001:500:c::1, 2001:500:e::1, 2001:500:f::1, 2001:500:40::1, 2001:500:48::1, TCP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K)
  • isoc.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2ecmy1wv67.isoc.org/A 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