View on GitHub

DNSViz: A DNS visualization tool

secure.d3a6n3.rootcanary.net

Updated: 2020-04-19 17:33:52 UTC (1707 days ago) Update now
« 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 (2)
  • secure.d3a6n3.rootcanary.net/A
  • secure.d3a6n3.rootcanary.net/AAAA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (1)
  • d3a6n3.rootcanary.net/DNSKEY (alg 6, id 45036)
Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • d3a6n3.rootcanary.net/DS (alg 6, id 45036)
  • net/DNSKEY (alg 8, id 24512)
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 36059)
  • net/DS (alg 8, id 35886)
  • rootcanary.net/DNSKEY (alg 8, id 25188)
  • rootcanary.net/DNSKEY (alg 8, id 64786)
  • rootcanary.net/DS (alg 8, id 64786)

Delegation statusDelegation status

Insecure (1)
  • rootcanary.net to d3a6n3.rootcanary.net
Secure (2)
  • . to net
  • net to rootcanary.net

NoticesNotices

Errors (1)
  • d3a6n3.rootcanary.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • RRSIG d3a6n3.rootcanary.net/DNSKEY alg 6, id 45036: DNSSEC implementers are prohibited from implementing signing with DNSSEC algorithm 6 (DSANSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG d3a6n3.rootcanary.net/DNSKEY alg 6, id 45036: DNSSEC implementers are prohibited from implementing validation of DNSSEC algorithm 6 (DSANSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG secure.d3a6n3.rootcanary.net/A alg 6, id 45036: DNSSEC implementers are prohibited from implementing signing with DNSSEC algorithm 6 (DSANSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG secure.d3a6n3.rootcanary.net/A alg 6, id 45036: DNSSEC implementers are prohibited from implementing validation of DNSSEC algorithm 6 (DSANSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG secure.d3a6n3.rootcanary.net/AAAA alg 6, id 45036: DNSSEC implementers are prohibited from implementing signing with DNSSEC algorithm 6 (DSANSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG secure.d3a6n3.rootcanary.net/AAAA alg 6, id 45036: DNSSEC implementers are prohibited from implementing validation of DNSSEC algorithm 6 (DSANSEC3SHA1). See RFC 8624, Sec. 3.1.
  • d3a6n3.rootcanary.net/DS (alg 6, id 45036): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
  • d3a6n3.rootcanary.net/DS (alg 6, id 45036): DNSSEC implementers are prohibited from implementing signing with DS algorithm 3 (GOST 34.11-94). See RFC 8624, Sec. 3.2.
  • d3a6n3.rootcanary.net/DS (alg 6, id 45036): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
  • d3a6n3.rootcanary.net/DS (alg 6, id 45036): Generating cryptographic hashes using algorithm 3 (GOST 34.11-94) is not supported by this code, so the cryptographic status of the DS RR is unknown. See RFC 4035, Sec. 5.2.
  • d3a6n3.rootcanary.net/CNAME 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