View on GitHub

DNSViz: A DNS visualization tool

fiu.edu

Updated: 2021-03-16 17:43:13 UTC (1358 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • fiu.edu/A
  • fiu.edu/MX
  • fiu.edu/NS
  • fiu.edu/SOA
  • fiu.edu/TXT
Secure (2)
  • edu/SOA
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • fiu.edu/DNSKEY (alg 5, id 23637)
  • fiu.edu/DNSKEY (alg 5, id 40095)
  • fiu.edu/DNSKEY (alg 5, id 57646)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of fiu.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 62987)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

Insecure (1)
  • edu to fiu.edu
Secure (1)
  • . to edu

NoticesNotices

Warnings (15)
  • RRSIG fiu.edu/A alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/DNSKEY alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/DNSKEY alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/DNSKEY alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/DNSKEY alg 5, id 57646: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/DNSKEY alg 5, id 57646: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/DNSKEY alg 5, id 57646: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/MX alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/NS alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/SOA alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fiu.edu/TXT alg 5, id 40095: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • fiu.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fiu.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fiu.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 1ahsb2r64z.fiu.edu/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