View on GitHub

DNSViz: A DNS visualization tool

centene.com

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

RRset statusRRset status

Insecure (5)
  • centene.com/A
  • centene.com/MX
  • centene.com/NS
  • centene.com/SOA
  • centene.com/TXT
Secure (1)
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • centene.com/DNSKEY (alg 5, id 24481)
  • centene.com/DNSKEY (alg 5, id 34903)
  • centene.com/DNSKEY (alg 5, id 36432)
  • centene.com/DNSKEY (alg 5, id 61800)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of centene.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 58540)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • centene.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (204.107.40.10, 204.107.40.11, 204.145.114.10, 204.145.114.11)
  • centene.com/DNSKEY (alg 5, id 36432): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (204.145.114.10, 204.145.114.11, UDP_-_EDNS0_4096_D_KN)
  • centene.com/DNSKEY (alg 5, id 61800): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (204.107.40.10, 204.107.40.11, UDP_-_EDNS0_4096_D_KN)
  • centene.com/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (204.107.40.10, 204.107.40.11, 204.145.114.10, 204.145.114.11, TCP_-_EDNS0_4096_D_N)
Warnings (26)
  • RRSIG centene.com/A alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/A alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 24481: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 24481: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 34903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 34903: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/DNSKEY alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/MX alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/MX alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/NS alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/NS alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/SOA alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/SOA alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/TXT alg 5, id 36432: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG centene.com/TXT alg 5, id 61800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • centene.com/DNSKEY (alg 5, id 24481): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (204.145.114.10, 204.145.114.11, UDP_-_EDNS0_4096_D_KN)
  • centene.com/DNSKEY (alg 5, id 34903): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (204.107.40.10, 204.107.40.11, UDP_-_EDNS0_4096_D_KN)
  • centene.com/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (204.107.40.10, 204.107.40.11, 204.145.114.10, 204.145.114.11, UDP_-_EDNS0_512_D_KN)
  • centene.com/DNSKEY: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (204.107.40.10, 204.107.40.11, 204.145.114.10, 204.145.114.11, UDP_-_EDNS0_512_D_KN)
  • centene.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • centene.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • centene.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • flj6itzbd5.centene.com/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