View on GitHub

DNSViz: A DNS visualization tool

execsec.gov

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

RRset statusRRset status

Secure (5)
  • execsec.gov/A
  • execsec.gov/NS
  • execsec.gov/NSEC3PARAM
  • execsec.gov/SOA
  • execsec.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • execsec.gov/DNSKEY (alg 8, id 2137)
  • execsec.gov/DNSKEY (alg 8, id 54126)
  • execsec.gov/DS (alg 8, id 17770)
  • execsec.gov/DS (alg 8, id 2137)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
Non_existent (1)
  • execsec.gov/DNSKEY (alg 8, id 17770)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to execsec.gov

NoticesNotices

Errors (11)
  • RRSIG execsec.gov/DNSKEY alg 8, id 2137: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2024-10-12 23:49:31+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG execsec.gov/DNSKEY alg 8, id 2137: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2024-10-12 23:49:31+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG execsec.gov/DNSKEY alg 8, id 54126: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2024-10-12 23:49:31+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG execsec.gov/DNSKEY alg 8, id 54126: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 54 minutes after it expires at 2024-10-12 23:49:31+00:00. See RFC 4035, Sec. 5.3.3.
  • execsec.gov/CDNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.141.126.202, 199.141.126.206, 2600:12f0:0:ac04::202, 2600:12f0:0:ac04::206, UDP_-_NOEDNS_)
  • execsec.gov/CDS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.141.126.202, 199.141.126.206, 2600:12f0:0:ac04::202, 2600:12f0:0:ac04::206, UDP_-_NOEDNS_)
  • execsec.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • execsec.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • execsec.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • w4zaf.az4et.execsec.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • execsec.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • execsec.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • execsec.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • execsec.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • w4zaf.az4et.execsec.gov/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