View on GitHub

DNSViz: A DNS visualization tool

upf.edu

Updated: 2023-09-18 14:03:17 UTC (2 years 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

Secure (5)
  • upf.edu/A
  • upf.edu/MX
  • upf.edu/NS
  • upf.edu/SOA
  • upf.edu/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DNSKEY (alg 13, id 8957)
  • edu/DNSKEY (alg 8, id 24314)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DS (alg 13, id 35663)
  • upf.edu/DNSKEY (alg 5, id 22876)
  • upf.edu/DNSKEY (alg 5, id 25467)
  • upf.edu/DNSKEY (alg 5, id 31662)
  • upf.edu/DS (alg 5, id 22876)

Delegation statusDelegation status

Secure (2)
  • . to edu
  • edu to upf.edu

NoticesNotices

Warnings (28)
  • RRSIG upf.edu/A alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/A alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/MX alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/MX alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/NS alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/NS alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/SOA alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/SOA alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/TXT alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG upf.edu/TXT alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • edu to upf.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): ns1.upf.edu See RFC 1034, Sec. 4.2.2.
  • m5sdu8zr4q.upf.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • upf.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • upf.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • upf.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • upf.edu/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