View on GitHub

DNSViz: A DNS visualization tool

sandelman.ca

« 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 (6)
  • sandelman.ca/A
  • sandelman.ca/AAAA
  • sandelman.ca/MX
  • sandelman.ca/NS
  • sandelman.ca/SOA
  • sandelman.ca/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • ca/DNSKEY (alg 8, id 2134)
  • ca/DNSKEY (alg 8, id 35433)
  • ca/DS (alg 8, id 2134)
  • sandelman.ca/DNSKEY (alg 5, id 31306)
  • sandelman.ca/DNSKEY (alg 5, id 38386)
  • sandelman.ca/DNSKEY (alg 5, id 43875)
  • sandelman.ca/DNSKEY (alg 5, id 53073)
  • sandelman.ca/DS (alg 5, id 31306)
  • sandelman.ca/DS (alg 5, id 31306)
  • sandelman.ca/DS (alg 5, id 38386)
  • sandelman.ca/DS (alg 5, id 38386)

Delegation statusDelegation status

Secure (2)
  • . to ca
  • ca to sandelman.ca

NoticesNotices

Warnings (37)
  • RRSIG sandelman.ca/A alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/AAAA alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 31306: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 31306: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 31306: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 31306: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 38386: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/DNSKEY alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/MX alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/NS alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/SOA alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/TXT alg 5, id 43875: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • sandelman.ca/AAAA: 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • sandelman.ca/DNSKEY (alg 5, id 31306): 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • sandelman.ca/DNSKEY (alg 5, id 38386): 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • sandelman.ca/DNSKEY (alg 5, id 43875): 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • sandelman.ca/DNSKEY (alg 5, id 53073): 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • sandelman.ca/DS (alg 5, id 31306): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandelman.ca/DS (alg 5, id 31306): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandelman.ca/DS (alg 5, id 31306): 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.
  • sandelman.ca/DS (alg 5, id 31306): 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.
  • sandelman.ca/DS (alg 5, id 38386): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandelman.ca/DS (alg 5, id 38386): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandelman.ca/DS (alg 5, id 38386): 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.
  • sandelman.ca/DS (alg 5, id 38386): 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.
  • sandelman.ca/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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • sandelman.ca/SOA: 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • sandelman.ca/TXT: 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. (2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_K)
  • wjmbuvadhx.sandelman.ca/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sandelman.ca/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sandelman.ca/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