View on GitHub

DNSViz: A DNS visualization tool

coreraid.com

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

RRset statusRRset status

Bogus (4)
  • coreraid.com/MX
  • coreraid.com/NS
  • coreraid.com/SOA
  • coreraid.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • coreraid.com/DNSKEY (alg 13, id 2371)
  • coreraid.com/DNSKEY (alg 13, id 34505)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 4534)
  • com/DS (alg 13, id 19718)
  • coreraid.com/DS (alg 13, id 48956)
Non_existent (1)
  • coreraid.com/DNSKEY (alg 13, id 48956)

Delegation statusDelegation status

Bogus (1)
  • com to coreraid.com
Secure (1)
  • . to com

NoticesNotices

Errors (2)
  • com to coreraid.com: 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.192.132, 108.162.193.91, 172.64.32.132, 172.64.33.91, 173.245.58.132, 173.245.59.91, 2606:4700:50::adf5:3a84, 2606:4700:58::adf5:3b5b, 2803:f800:50::6ca2:c084, 2803:f800:50::6ca2:c15b, 2a06:98c1:50::ac40:2084, 2a06:98c1:50::ac40:215b, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • com to coreraid.com: 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. (108.162.192.132, 108.162.193.91, 172.64.32.132, 172.64.33.91, 173.245.58.132, 173.245.59.91, 2606:4700:50::adf5:3a84, 2606:4700:58::adf5:3b5b, 2803:f800:50::6ca2:c084, 2803:f800:50::6ca2:c15b, 2a06:98c1:50::ac40:2084, 2a06:98c1:50::ac40:215b, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
Warnings (4)
  • ./DNSKEY (alg 8, id 20326): 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. (170.247.170.2, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 30903): 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. (170.247.170.2, UDP_-_EDNS0_4096_D_KN)
  • com/DS (alg 13, id 19718): 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. (170.247.170.2, UDP_-_EDNS0_4096_D_KN)
  • com/DS (alg 13, id 19718): 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. (170.247.170.2, UDP_-_EDNS0_4096_D_KN)

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