View on GitHub

DNSViz: A DNS visualization tool

suntrust.com

Updated: 2020-08-06 16:17:32 UTC (1413 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • suntrust.com/A
  • suntrust.com/MX
  • suntrust.com/NS
  • suntrust.com/SOA
  • suntrust.com/TXT
Secure (3)
  • com/SOA
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of suntrust.com/DS
  • com/DNSKEY (alg 8, id 24966)
  • com/DNSKEY (alg 8, id 30909)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • suntrust.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (167.181.247.10)
  • suntrust.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (167.181.247.10, UDP_-_NOEDNS_)
  • suntrust.com/DNSKEY: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_512_D_K)
  • suntrust.com/MX: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_512_D_K)
  • suntrust.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (167.181.247.10, UDP_-_NOEDNS_)
  • suntrust.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • com to suntrust.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns1.p25.dynect.net, ns2.p25.dynect.net, ns3.p25.dynect.net, ns4.p25.dynect.net See RFC 1034, Sec. 4.2.2.
  • suntrust.com/A: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_4096_D_K)
  • suntrust.com/MX: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_4096_D_K)
  • suntrust.com/NS: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_4096_D_K)
  • suntrust.com/SOA: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • suntrust.com/TXT: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (167.181.12.68, 167.181.192.10, UDP_-_EDNS0_4096_D_K)
  • suntrust.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nvz9a6wqf4.suntrust.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • suntrust.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • suntrust.com/DNSKEY 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