View on GitHub

DNSViz: A DNS visualization tool

sandelman.ca

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

RRset statusRRset status

Bogus (1)
  • sandelman.ca/SOA
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

Bogus (1)
  • sandelman.ca/DNSKEY (alg 13, id 35158)
Secure (18)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • ca/DNSKEY (alg 8, id 34254)
  • ca/DNSKEY (alg 8, id 48662)
  • ca/DS (alg 8, id 48662)
  • sandelman.ca/DNSKEY (alg 5, id 13338)
  • sandelman.ca/DNSKEY (alg 5, id 28834)
  • 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 4926)
  • sandelman.ca/DNSKEY (alg 5, id 49308)
  • sandelman.ca/DNSKEY (alg 5, id 53073)
  • sandelman.ca/DNSKEY (alg 5, id 54702)
  • 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

Errors (36)
  • ca to sandelman.ca: 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. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ca to sandelman.ca: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/AAAA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 13, id 35158): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 13338): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 13338): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 28834): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 31306): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 31306): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 38386): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 38386): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 43875): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 43875): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 4926): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 4926): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 49308): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 49308): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 53073): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 53073): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 54702): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 54702): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sandelman.ca/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sandelman.ca/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sandelman.ca/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • 67lzspx9eb.sandelman.ca/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sandelman.ca/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • sandelman.ca/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (77)
  • RRSIG sandelman.ca/A alg 5, id 13338: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • 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/A alg 5, id 4926: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/A alg 5, id 49308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/A alg 5, id 53073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandelman.ca/A alg 5, id 54702: 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 13338: 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/AAAA alg 5, id 4926: 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 49308: 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 53073: 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 54702: 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 28834: 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 28834: 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 28834: 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 28834: 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 28834: 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 28834: 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 28834: 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 28834: 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 28834: 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 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 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 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 38386: 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 13338: 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/MX alg 5, id 4926: 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 49308: 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 53073: 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 54702: 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 13338: 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/NS alg 5, id 4926: 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 49308: 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 53073: 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 54702: 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 13338: 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/SOA alg 5, id 4926: 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 49308: 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 53073: 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 54702: 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 13338: 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.
  • RRSIG sandelman.ca/TXT alg 5, id 4926: 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 49308: 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 53073: 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 54702: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • sandelman.ca/DNSKEY (alg 13, id 35158): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (97.107.133.15, 2600:3c03::f03c:91ff:fe96:e8ef, UDP_-_EDNS0_4096_D_KN)
  • sandelman.ca/DNSKEY (alg 5, id 28834): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (209.87.249.18, 2607:f0b0:f::babe:f00d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 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/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 67lzspx9eb.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