View on GitHub

DNSViz: A DNS visualization tool

www.powercastco.com

Updated: 2023-05-02 17:01:02 UTC (523 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

Secure (2)
  • powercastco.com/CNAME (NODATA)
  • powercastco.com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC proving non-existence of powercastco.com/CNAME
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 46551)
  • com/DS (alg 8, id 30909)
  • powercastco.com/DNSKEY (alg 13, id 23285)
  • powercastco.com/DS (alg 13, id 23285)
  • powercastco.com/DS (alg 13, id 23285)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to powercastco.com

NoticesNotices

Errors (5)
  • NSEC proving non-existence of powercastco.com/CNAME: The following queries resulted in an answer response, even though the NSEC records indicate that the queried names don't exist: cyg3wr2omx.powercastco.com/A See RFC 4035, Sec. 3.1.3.2.
  • NSEC proving non-existence of powercastco.com/CNAME: The following queries resulted in an answer response, even though the NSEC records indicate that the queried names don't exist: cyg3wr2omx.powercastco.com/A See RFC 4035, Sec. 3.1.3.2.
  • NSEC proving non-existence of powercastco.com/CNAME: The following queries resulted in an answer response, even though the NSEC records indicate that the queried names don't exist: www.powercastco.com/A See RFC 4035, Sec. 3.1.3.2.
  • NSEC proving non-existence of powercastco.com/CNAME: The following queries resulted in an answer response, even though the NSEC records indicate that the queried names don't exist: www.powercastco.com/A See RFC 4035, Sec. 3.1.3.2.
  • www.powercastco.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • powercastco.com/DS (alg 13, id 23285): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • powercastco.com/DS (alg 13, id 23285): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • powercastco.com/DS (alg 13, id 23285): 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.
  • powercastco.com/DS (alg 13, id 23285): 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.
  • powercastco.com/DS (alg 13, id 23285): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
  • powercastco.com/DS (alg 13, id 23285): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.

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