View on GitHub

DNSViz: A DNS visualization tool

conseco.com

Updated: 2022-07-01 01:41:24 UTC (743 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • ./DNSKEY (alg 8, id 47671)
  • NSEC3 proving non-existence of conseco.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 37269)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • conseco.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (205.144.112.15)
  • conseco.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (205.144.112.15)
  • conseco.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (12.31.249.90)
  • conseco.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (12.31.249.90, UDP_-_NOEDNS_)
  • conseco.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, UDP_-_EDNS0_4096_D_KN)
  • conseco.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • conseco.com/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • conseco.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (12.31.249.90, UDP_-_NOEDNS_)
  • conseco.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, UDP_-_EDNS0_4096_D_KN)
  • conseco.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, TCP_-_EDNS0_4096_D_N)
  • conseco.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • conseco.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.144.112.15, UDP_-_EDNS0_4096_D_KN)
  • conseco.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • amdopncg6f.conseco.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • conseco.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • conseco.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • conseco.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • com to conseco.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ext-d1.conseco.com, ext-d2.conseco.com See RFC 1034, Sec. 4.2.2.
  • com to conseco.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: extdns1.banklife.com, ns1.conseco.com, ns2.conseco.com See RFC 1034, Sec. 4.2.2.
  • com to conseco.com: The glue address(es) for extdns1.banklife.com (12.31.249.90) differed from its authoritative address(es) (205.144.112.15). See RFC 1034, Sec. 4.2.2.

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