View on GitHub

DNSViz: A DNS visualization tool

bep.gov

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

RRset statusRRset status

Secure (12)
  • bep.gov/A
  • bep.gov/MX
  • bep.gov/NS
  • bep.gov/NSEC3PARAM
  • bep.gov/NSEC3PARAM
  • bep.gov/NSEC3PARAM
  • bep.gov/NSEC3PARAM
  • bep.gov/NSEC3PARAM
  • bep.gov/SOA
  • bep.gov/SOA
  • bep.gov/SOA
  • bep.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • bep.gov/DNSKEY (alg 8, id 23388)
  • bep.gov/DNSKEY (alg 8, id 34504)
  • bep.gov/DS (alg 8, id 34504)
  • bep.gov/DS (alg 8, id 34504)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • bep.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (164.95.20.53)
  • bep.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (164.95.20.53, 2610:108:3100:100a::20:53, UDP_-_EDNS0_512_D_KN)
  • bep.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (2610:108:3100:100a::20:53, UDP_-_EDNS0_4096_D_KN)
  • bep.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (164.95.20.53, TCP_-_EDNS0_4096_D_N)
  • bep.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (164.95.20.53, UDP_-_EDNS0_4096_D_KN)
  • bep.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (2610:108:3100:100a::20:53, UDP_-_EDNS0_4096_D_KN)
  • t2e6r05p97.bep.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bep.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • bep.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • bep.gov/DS (alg 8, id 34504): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bep.gov/DS (alg 8, id 34504): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bep.gov/DS (alg 8, id 34504): 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.
  • bep.gov/DS (alg 8, id 34504): 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.
  • t2e6r05p97.bep.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bep.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bep.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