View on GitHub

DNSViz: A DNS visualization tool

express-scripts.com

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

RRset statusRRset status

Bogus (5)
  • express-scripts.com/A
  • express-scripts.com/MX
  • express-scripts.com/SOA
  • express-scripts.com/TXT
  • express-scripts.com/TXT
Secure (2)
  • express-scripts.com/NS
  • express-scripts.com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 59354)
  • com/DNSKEY (alg 13, id 956)
  • com/DS (alg 13, id 19718)
  • express-scripts.com/DNSKEY (alg 8, id 258)
  • express-scripts.com/DNSKEY (alg 8, id 58716)
  • express-scripts.com/DNSKEY (alg 8, id 59224)
  • express-scripts.com/DNSKEY (alg 8, id 63919)
  • express-scripts.com/DS (alg 8, id 38587)
  • express-scripts.com/DS (alg 8, id 40696)
  • express-scripts.com/DS (alg 8, id 63919)
  • express-scripts.com/DS (alg 8, id 63919)
Non_existent (2)
  • express-scripts.com/DNSKEY (alg 8, id 38587)
  • express-scripts.com/DNSKEY (alg 8, id 40696)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to express-scripts.com

NoticesNotices

Errors (60)
  • RRSIG express-scripts.com/A alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 02:11:33+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/A alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-15 00:44:07+00:00) is 2 hours, 37 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/A alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 02:11:33+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/A alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-15 00:44:07+00:00) is 2 hours, 37 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 258: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 58716: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 59224: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: The Signature Expiration field of the RRSIG RR (2024-07-13 07:19:19+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/DNSKEY alg 8, id 63919: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2024-07-15 05:43:53+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/MX alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 00:01:08+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/MX alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-14 23:48:16+00:00) is 3 hours, 32 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/MX alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 00:01:08+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/MX alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-14 23:48:16+00:00) is 3 hours, 32 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/NS alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 05:53:24+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/NS alg 8, id 258: With a TTL of 43200 the RRSIG RR can be in the cache of a non-validating resolver until 10 hours, 38 minutes after it expires at 2024-07-15 04:42:15+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/NS alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 05:53:24+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/NS alg 8, id 58716: With a TTL of 43200 the RRSIG RR can be in the cache of a non-validating resolver until 10 hours, 38 minutes after it expires at 2024-07-15 04:42:15+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/SOA alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 12:05:54+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/SOA alg 8, id 258: With a TTL of 43200 the RRSIG RR can be in the cache of a non-validating resolver until 2 hours, 38 minutes after it expires at 2024-07-15 12:42:19+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/SOA alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 12:05:54+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/SOA alg 8, id 58716: With a TTL of 43200 the RRSIG RR can be in the cache of a non-validating resolver until 2 hours, 38 minutes after it expires at 2024-07-15 12:42:19+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG express-scripts.com/TXT alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-13 06:28:15+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/TXT alg 8, id 258: The Signature Expiration field of the RRSIG RR (2024-07-15 02:01:08+00:00) is 1 hour, 20 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/TXT alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-13 06:28:15+00:00) is 1 day in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG express-scripts.com/TXT alg 8, id 58716: The Signature Expiration field of the RRSIG RR (2024-07-15 02:01:08+00:00) is 1 hour, 20 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • 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. (167.18.104.150, TCP_-_EDNS0_4096_D_KN)
  • express-scripts.com/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 7cial.s38mi.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.
  • express-scripts.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • express-scripts.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • express-scripts.com/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • 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.
  • express-scripts.com/DS (alg 8, id 63919): 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 63919): 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 63919): 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 63919): 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.

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