View on GitHub

DNSViz: A DNS visualization tool

myfdic.gov

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

RRset statusRRset status

Insecure (4)
  • myfdic.gov/MX
  • myfdic.gov/NS
  • myfdic.gov/SOA
  • myfdic.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • myfdic.gov/DNSKEY (alg 8, id 16552)
  • myfdic.gov/DNSKEY (alg 8, id 29724)
  • myfdic.gov/DNSKEY (alg 8, id 42856)
  • myfdic.gov/DNSKEY (alg 8, id 48186)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • NSEC3 proving non-existence of myfdic.gov/DS
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to myfdic.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (8)
  • NSEC3 proving non-existence of myfdic.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of myfdic.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • myfdic.gov zone: The following NS name(s) did not resolve to address(es): 72.246.0.10, 23.205.121.134, 23.73.133.141, 23.73.134.141, 193.108.152.143, 23.207.197.166, 72.246.192.168, 104.107.116.17, 23.14.128.185, 23.73.133.237, 23.73.134.237, 193.108.155.34, 2.18.25.37, 60.254.128.45, 104.122.95.88, 72.247.124.98
  • myfdic.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1e4a8bt2sw.myfdic.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • myfdic.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • myfdic.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • myfdic.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • NSEC3 proving non-existence of myfdic.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of myfdic.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • gov to myfdic.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): 23.14.128.185, 193.108.155.34, 23.73.134.237, 2.18.25.37, 193.108.152.143, 23.205.121.134, 104.122.95.88, 60.254.128.45, 23.73.133.141, 72.246.0.10, 72.247.124.98, 104.107.116.17, 23.73.133.237, 72.246.192.168, 23.207.197.166, 23.73.134.141 See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • myfdic.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 1e4a8bt2sw.myfdic.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • myfdic.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • myfdic.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • myfdic.gov/AAAA 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