View on GitHub

DNSViz: A DNS visualization tool

chase.com

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

RRset statusRRset status

Insecure (5)
  • chase.com/A
  • chase.com/MX
  • chase.com/NS
  • chase.com/SOA
  • chase.com/TXT
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of chase.com/DS
  • com/DNSKEY (alg 8, id 15549)
  • com/DNSKEY (alg 8, id 30909)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Insecure (1)
  • com to chase.com
Secure (1)
  • . to com

NoticesNotices

Errors (14)
  • chase.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153)
  • chase.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153)
  • chase.com/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, UDP_-_NOEDNS_)
  • chase.com/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • chase.com/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • chase.com/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, UDP_-_NOEDNS_)
  • chase.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, TCP_-_NOEDNS_)
  • chase.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • chase.com/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (159.53.110.152, 159.53.110.153, UDP_-_NOEDNS_)
  • chase.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • frmcptq0oe.chase.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • chase.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • chase.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • chase.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • chase.com/TXT: 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. (159.53.46.53, 159.53.78.53, 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