View on GitHub

DNSViz: A DNS visualization tool

ipfire.org

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

RRset statusRRset status

Secure (7)
  • ipfire.org/A
  • ipfire.org/AAAA
  • ipfire.org/MX
  • ipfire.org/NS
  • ipfire.org/NSEC3PARAM
  • ipfire.org/SOA
  • ipfire.org/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • ipfire.org/DNSKEY (alg 10, id 6536)
  • ipfire.org/DNSKEY (alg 8, id 54142)
  • ipfire.org/DNSKEY (alg 8, id 6900)
  • ipfire.org/DS (alg 8, id 54142)
  • org/DNSKEY (alg 8, id 15843)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 41346)
  • org/DS (alg 8, id 26974)

Delegation statusDelegation status

Secure (2)
  • . to org
  • org to ipfire.org

NoticesNotices

Errors (2)
  • ipfire.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • bowg8rnikh.ipfire.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
  • RRSIG ipfire.org/A alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/AAAA alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/DNSKEY alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/DNSKEY alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/DNSKEY alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/MX alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/NS alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/NSEC3PARAM alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/SOA alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ipfire.org/TXT alg 10, id 6536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • ipfire.org/DNSKEY (alg 10, id 6536): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (74.113.60.134, UDP_-_EDNS0_4096_D_KN)
  • ipfire.org/DNSKEY (alg 8, id 54142): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (74.113.60.134, UDP_-_EDNS0_4096_D_KN)
  • ipfire.org/DNSKEY (alg 8, id 6900): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (74.113.60.134, UDP_-_EDNS0_4096_D_KN)
  • ipfire.org/DS (alg 8, id 54142): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ipfire.org/DS (alg 8, id 54142): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ipfire.org/MX: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (74.113.60.134, UDP_-_EDNS0_4096_D_KN)
  • ipfire.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bowg8rnikh.ipfire.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ipfire.org/DNSKEY 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