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

Bogus (1)
  • defcon.org/SOA
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 (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • 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 33209)
  • org/DNSKEY (alg 7, id 37022)
  • org/DNSKEY (alg 7, id 9795)
  • org/DS (alg 7, id 9795)
  • org/DS (alg 7, id 9795)

Delegation statusDelegation status

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

NoticesNotices

Errors (20)
  • RRSIG defcon.org/A alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-02 20:04:51+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • 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 10 days after it expires at 2020-04-25 07:18:11+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/AAAA alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-02 20:04:51+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • 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 10 days after it expires at 2020-04-25 07:18:11+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/DNSKEY alg 10, id 38292: The Signature Expiration field of the RRSIG RR (2020-04-01 19:56:31+00:00) is 6 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 38292: The Signature Expiration field of the RRSIG RR (2020-04-01 19:56:31+00:00) is 6 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-01 19:56:31+00:00) is 6 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG defcon.org/DNSKEY alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-01 19:56:31+00:00) is 6 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG defcon.org/MX alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-02 20:04:51+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • 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 10 days after it expires at 2020-04-25 07:18:11+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/NS alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-02 20:04:51+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • 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 10 days after it expires at 2020-04-25 07:18:11+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/SOA alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-03 13:04:43+00:00) is 4 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG defcon.org/SOA alg 10, id 50153: With a TTL of 2419200 the RRSIG RR can be in the cache of a non-validating resolver until 9 days after it expires at 2020-04-26 00:43:47+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG defcon.org/TXT alg 10, id 50153: The Signature Expiration field of the RRSIG RR (2020-04-02 20:04:51+00:00) is 5 days in the past. See RFC 4035, Sec. 5.3.1.
  • 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 10 days after it expires at 2020-04-25 07:18:11+00:00. See RFC 4035, Sec. 5.3.3.
  • org to defcon.org: 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. (64.87.1.238, 2600:4402:c004::3, TCP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K)
  • kz7wtx56b1.defcon.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 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.
Warnings (44)
  • 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/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/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 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/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 37022: 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 37022: 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/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/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/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 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 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 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 9795: 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 9795): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 9795): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 9795): 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 9795): 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.
  • kz7wtx56b1.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