View on GitHub

DNSViz: A DNS visualization tool

flyhealthy.gov

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

RRset statusRRset status

Bogus (5)
  • flyhealthy.gov/A
  • flyhealthy.gov/NS
  • flyhealthy.gov/NSEC3PARAM
  • flyhealthy.gov/SOA
  • flyhealthy.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • flyhealthy.gov/DNSKEY (alg 10, id 10656)
  • flyhealthy.gov/DNSKEY (alg 10, id 14721)
  • flyhealthy.gov/DNSKEY (alg 10, id 16088)
  • flyhealthy.gov/DNSKEY (alg 10, id 37580)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • flyhealthy.gov/DS (alg 10, id 59628)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • flyhealthy.gov/DNSKEY (alg 10, id 59628)

Delegation statusDelegation status

Bogus (1)
  • gov to flyhealthy.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (6)
  • gov to flyhealthy.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_KN)
  • gov to flyhealthy.gov: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_KN)
  • flyhealthy.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 29v07zuyji.flyhealthy.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • flyhealthy.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • flyhealthy.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
  • RRSIG flyhealthy.gov/A alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 10656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 10656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 10656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 10656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 14721: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 14721: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 14721: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 14721: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/DNSKEY alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/NS alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/NSEC3PARAM alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/SOA alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG flyhealthy.gov/TXT alg 10, id 37580: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • flyhealthy.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 29v07zuyji.flyhealthy.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • flyhealthy.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • flyhealthy.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • flyhealthy.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