View on GitHub

DNSViz: A DNS visualization tool

sapphire.cfts.co

Updated: 2020-06-01 17:31:04 UTC (1668 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 (1)
  • sapphire.cfts.co/A

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • cfts.co/DNSKEY (alg 8, id 17491)
  • cfts.co/DNSKEY (alg 8, id 48084)
  • cfts.co/DS (alg 8, id 17491)
  • cfts.co/DS (alg 8, id 17491)
  • co/DNSKEY (alg 8, id 10384)
  • co/DNSKEY (alg 8, id 43834)
  • co/DNSKEY (alg 8, id 63993)
  • co/DNSKEY (alg 8, id 64278)
  • co/DS (alg 8, id 10384)
  • co/DS (alg 8, id 10384)
  • co/DS (alg 8, id 43834)
  • co/DS (alg 8, id 43834)

Delegation statusDelegation status

Secure (2)
  • . to co
  • co to cfts.co

NoticesNotices

Errors (2)
  • sapphire.cfts.co/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • cfts.co/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • cfts.co/DS (alg 8, id 17491): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cfts.co/DS (alg 8, id 17491): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cfts.co/DS (alg 8, id 17491): 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.
  • cfts.co/DS (alg 8, id 17491): 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.
  • cfts.co/DS (alg 8, id 17491): 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.
  • cfts.co/DS (alg 8, id 17491): 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.
  • co/DS (alg 8, id 10384): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • co/DS (alg 8, id 10384): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • co/DS (alg 8, id 10384): 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.
  • co/DS (alg 8, id 10384): 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.
  • co/DS (alg 8, id 43834): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • co/DS (alg 8, id 43834): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • co/DS (alg 8, id 43834): 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.
  • co/DS (alg 8, id 43834): 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.
  • sapphire.cfts.co/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • cfts.co/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