express-scripts.com
Updated:
2023-01-09 03:55:51 UTC (685 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- express-scripts.com/A
- express-scripts.com/NS
- express-scripts.com/SOA
- express-scripts.com/SOA
- express-scripts.com/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 53929)
- com/DS (alg 8, id 30909)
- express-scripts.com/DS (alg 8, id 38587)
- express-scripts.com/DS (alg 8, id 40696)
Non_existent (4)
- express-scripts.com/DNSKEY (alg 8, id 38587)
- express-scripts.com/DNSKEY (alg 8, id 40696)
- express-scripts.com/DNSKEY (alg 8, id 46578)
- express-scripts.com/DNSKEY (alg 8, id 9453)
Delegation status
Bogus (1)
- com to express-scripts.com
Secure (1)
- . to com
Notices
Errors (13)
- com to express-scripts.com: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- express-scripts.com/AAAA: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (167.18.104.150, 167.211.104.150, TCP_-_EDNS0_4096_D_KN)
- express-scripts.com/DNSKEY: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (167.18.104.150, TCP_-_EDNS0_4096_D_KN)
- express-scripts.com/DNSKEY: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (167.211.104.150, TCP_-_EDNS0_4096_D_KN)
- express-scripts.com/MX: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (167.211.104.150, TCP_-_EDNS0_4096_D_KN)
- express-scripts.com/MX: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (167.18.104.150, TCP_-_EDNS0_4096_D_KN)
- express-scripts.com/SOA: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (167.18.104.150, 167.211.104.150, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_0x20)
- express-scripts.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (167.18.104.150, 167.211.104.150, TCP_-_EDNS0_4096_D_N)
- express-scripts.com/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (167.18.104.150, TCP_-_EDNS0_4096_D_KN)
- express-scripts.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- o216yengax.express-scripts.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- express-scripts.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- express-scripts.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- express-scripts.com/DS (alg 8, id 40696): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- express-scripts.com/DS (alg 8, id 40696): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- express-scripts.com/DS (alg 8, id 40696): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- express-scripts.com/DS (alg 8, id 40696): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
