View on GitHub

DNSViz: A DNS visualization tool

ferc.gov

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

RRset statusRRset status

Bogus (9)
  • ferc.gov/A
  • ferc.gov/MX
  • ferc.gov/NS
  • ferc.gov/NSEC3PARAM
  • ferc.gov/NSEC3PARAM
  • ferc.gov/NSEC3PARAM
  • ferc.gov/NSEC3PARAM
  • ferc.gov/SOA
  • ferc.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • ferc.gov/DNSKEY (alg 7, id 37071)
  • ferc.gov/DS (alg 7, id 37071)
  • ferc.gov/DS (alg 7, id 37071)
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (12)
  • ferc.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.240, 204.87.17.241, 216.230.6.242, 216.230.6.246, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.240, 204.87.17.241, 216.230.6.242, 216.230.6.246, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ferc.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.240, 204.87.17.241, 216.230.6.242, 216.230.6.246, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.240, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.241, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.230.6.242, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.230.6.246, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.240, 204.87.17.241, 216.230.6.242, 216.230.6.246, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ferc.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.87.17.240, 204.87.17.241, 216.230.6.242, 216.230.6.246, UDP_-_EDNS0_4096_D_KN)
  • ferc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • yk0b4nto7r.ferc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ferc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • RRSIG ferc.gov/DNSKEY alg 7, id 37071: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ferc.gov/DNSKEY alg 7, id 37071: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • ferc.gov/DS (alg 7, id 37071): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ferc.gov/DS (alg 7, id 37071): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ferc.gov/DS (alg 7, id 37071): 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.
  • ferc.gov/DS (alg 7, id 37071): 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.
  • ferc.gov/DNSKEY 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