View on GitHub

DNSViz: A DNS visualization tool

fincen.gov

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • fincen.gov/DNSKEY (alg 8, id 37399)
  • fincen.gov/DNSKEY (alg 8, id 41748)
  • fincen.gov/DS (alg 8, id 37399)
  • fincen.gov/DS (alg 8, id 37399)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • fincen.gov/NS: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2606:4700:5a::ac40:3595, UDP_-_NOEDNS_)
  • fincen.gov/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2606:4700:5a::ac40:3595, UDP_-_EDNS0_4096_D_KN)
  • fincen.gov/NS: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2606:4700:5a::ac40:3595, UDP_-_EDNS0_4096_D_KN)
  • fincen.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 9c0frhdp8j.fincen.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • fincen.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (172.64.52.110, 172.64.53.149, 2606:4700:52::ac40:346e, 2606:4700:5a::ac40:3595, UDP_-_EDNS0_512_D_KN)
  • fincen.gov/DS (alg 8, id 37399): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fincen.gov/DS (alg 8, id 37399): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fincen.gov/DS (alg 8, id 37399): 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.
  • fincen.gov/DS (alg 8, id 37399): 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.
  • fincen.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fincen.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 9c0frhdp8j.fincen.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