View on GitHub

DNSViz: A DNS visualization tool

defcon.org

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

RRset statusRRset status

Secure (6)
  • defcon.org/A
  • defcon.org/AAAA
  • defcon.org/MX
  • defcon.org/NS
  • defcon.org/SOA
  • defcon.org/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • defcon.org/DNSKEY (alg 10, id 38292)
  • defcon.org/DNSKEY (alg 10, id 50153)
  • defcon.org/DS (alg 10, id 38292)
  • defcon.org/DS (alg 10, id 50153)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 21869)
  • org/DNSKEY (alg 7, id 27353)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 17883)

Delegation statusDelegation status

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

NoticesNotices

Errors (10)
  • RRSIG defcon.org/A alg 10, id 50153: With a TTL of 2419200 the RRSIG RR can be in the cache of a non-validating resolver until 17 days after it expires at 2020-08-16 20:27:35+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/AAAA alg 10, id 50153: With a TTL of 2419200 the RRSIG RR can be in the cache of a non-validating resolver until 17 days after it expires at 2020-08-16 20:27:35+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/MX alg 10, id 50153: With a TTL of 2419200 the RRSIG RR can be in the cache of a non-validating resolver until 19 days after it expires at 2020-08-15 16:13:27+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/NS alg 10, id 50153: With a TTL of 2419200 the RRSIG RR can be in the cache of a non-validating resolver until 19 days after it expires at 2020-08-15 16:13:27+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/TXT alg 10, id 50153: With a TTL of 2419200 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2020-09-02 04:02:33+00:00. See RFC 4035, Sec. 5.3.3.
  • defcon.org/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2605:9080:1089:d000::197, UDP_-_EDNS0_512_D_K)
  • defcon.org/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2605:9080:1089:d000::197, UDP_-_EDNS0_512_D_K)
  • defcon.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • defcon.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • suzw4dhfxb.defcon.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (28)
  • RRSIG defcon.org/A alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/AAAA alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 38292: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 38292: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/DS alg 7, id 21869: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/DS alg 7, id 21869: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/MX alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/NS alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/SOA alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG defcon.org/TXT alg 10, id 50153: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 21869: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 21869: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 21869: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • defcon.org/DNSKEY (alg 10, id 38292): 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. (2600:4402:c004::3, UDP_-_EDNS0_4096_D_K)
  • defcon.org/DNSKEY (alg 10, id 50153): 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. (2600:4402:c004::3, UDP_-_EDNS0_4096_D_K)
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): 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.
  • org/DS (alg 7, id 17883): 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.
  • defcon.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • defcon.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • defcon.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • suzw4dhfxb.defcon.org/A 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