centene.com
Updated:
2020-04-07 20:51:31 UTC (1690 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- centene.com/A
- centene.com/MX
- centene.com/NS
- centene.com/NS
- centene.com/SOA
- centene.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/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 (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of centene.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 56311)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to centene.com
Secure (1)
- . to com
Notices
Errors (7)
- centene.com zone: The following NS name(s) did not resolve to address(es): ns5.centene.com, ns6.centene.com
- 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/AAAA: The response (100 bytes) was malformed. (204.107.40.10, 204.107.40.11, 204.145.114.10, 204.145.114.11, UDP_-_NOEDNS_)
- 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_K)
- 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_K)
- 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)
- centene.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
- 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_K)
- 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_K)
- 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_K)
- 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_K)
- com to centene.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): ns6.centene.com, ns5.centene.com See RFC 1034, Sec. 4.2.2.
- centene.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- v8nsjoz392.centene.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
