View on GitHub

DNSViz: A DNS visualization tool

eia.gov

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

RRset statusRRset status

Secure (8)
  • eia.gov/A
  • eia.gov/AAAA
  • eia.gov/MX
  • eia.gov/NS
  • eia.gov/SOA
  • eia.gov/SOA
  • eia.gov/TXT
  • eia.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • eia.gov/DNSKEY (alg 5, id 34806)
  • eia.gov/DNSKEY (alg 5, id 35626)
  • eia.gov/DNSKEY (alg 5, id 48502)
  • eia.gov/DS (alg 5, id 34806)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Warnings (39)
  • RRSIG eia.gov/A alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/A alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/A alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/AAAA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/AAAA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/AAAA alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 35626: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 35626: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 48502: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/DNSKEY alg 5, id 48502: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/MX alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/MX alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/MX alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/NS alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/NS alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/NS alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/SOA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/SOA alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/SOA alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG eia.gov/TXT alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/TXT alg 5, id 34806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG eia.gov/TXT alg 5, id 34806: The value of the Signature Inception field of the RRSIG RR (2022-09-26 17:32:45+00:00) is within possible clock skew range (1 minute) of the current time (2022-09-26 17:34:05+00:00). See RFC 4035, Sec. 5.3.1.
  • eia.gov/DNSKEY (alg 5, id 35626): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.254.135.9, 2607:f368:1000:1001::1009, TCP_-_EDNS0_4096_D_KN)
  • eia.gov/DNSKEY (alg 5, id 48502): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.254.159.231, UDP_-_EDNS0_4096_D_KN)
  • eia.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (205.254.135.9, 205.254.159.231, 2607:f368:1000:1001::1009, UDP_-_EDNS0_512_D_KN)
  • eia.gov/DNSKEY: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (205.254.135.9, 205.254.159.231, 2607:f368:1000:1001::1009, UDP_-_EDNS0_512_D_KN)
  • eia.gov/DS (alg 5, id 34806): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • eia.gov/DS (alg 5, id 34806): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov to eia.gov: Authoritative AAAA records exist for phantom.eia.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • eia.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • j9faxw5vly.eia.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eia.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eia.gov/CNAME 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