View on GitHub

DNSViz: A DNS visualization tool

pettai.se

« 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 (6)
  • pettai.se/A
  • pettai.se/AAAA
  • pettai.se/MX
  • pettai.se/NS
  • pettai.se/SOA
  • pettai.se/TXT
Secure (1)
  • se/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • pettai.se/DNSKEY (alg 5, id 34560)
  • pettai.se/DNSKEY (alg 8, id 40906)
Secure (6)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC proving non-existence of pettai.se/DS
  • se/DNSKEY (alg 8, id 17395)
  • se/DNSKEY (alg 8, id 59407)
  • se/DS (alg 8, id 59407)

Delegation statusDelegation status

Insecure (1)
  • se to pettai.se
Secure (1)
  • . to se

NoticesNotices

Errors (6)
  • pettai.se zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2001:6b0:8::88)
  • pettai.se zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (193.10.5.82, 2001:6b0:8::82)
  • pettai.se/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (193.10.5.82, 2001:6b0:8::82, UDP_-_EDNS0_4096_D_KN)
  • pettai.se/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (193.10.5.82, 2001:6b0:8::82, UDP_-_EDNS0_4096_D_KN)
  • pettai.se/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2001:6b0:8::88, TCP_-_EDNS0_4096_D_N)
  • u2gxipe1y7.pettai.se/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • RRSIG pettai.se/A alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/AAAA alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/DNSKEY alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/DNSKEY alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/MX alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/NS alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/SOA alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pettai.se/TXT alg 5, id 34560: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • pettai.se/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • pettai.se/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • u2gxipe1y7.pettai.se/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • pettai.se/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