View on GitHub

DNSViz: A DNS visualization tool

activity.basalam.com

« 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 (3)
  • 405c8884ed3fb75cfc1386aff2cdeea2.cdn.cafebazaar.cloud/A
  • activity.basalam.com/CNAME
  • cafebazaar.cloud/SOA
Secure (3)
  • cloud/SOA
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • basalam.com/DNSKEY (alg 13, id 1638)
  • basalam.com/DNSKEY (alg 13, id 63298)
Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of basalam.com/DS
  • NSEC3 proving non-existence of cafebazaar.cloud/DS
  • cloud/DNSKEY (alg 8, id 2538)
  • cloud/DNSKEY (alg 8, id 49804)
  • cloud/DS (alg 8, id 49804)
  • cloud/DS (alg 8, id 49804)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 38535)
  • com/DS (alg 8, id 30909)
Non_existent (1)
  • activity.basalam.com/DNSKEY (alg 13, id 63298)

Delegation statusDelegation status

Insecure (3)
  • cafebazaar.cloud to cdn.cafebazaar.cloud
  • cloud to cafebazaar.cloud
  • com to basalam.com
Secure (2)
  • . to cloud
  • . to com

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of cafebazaar.cloud/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of cafebazaar.cloud/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG activity.basalam.com/CNAME alg 13, id 63298: The Signer's Name field of the RRSIG RR (activity.basalam.com) does not match the name of the zone containing the RRset (basalam.com). See RFC 4035, Sec. 5.3.1.
  • activity.basalam.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • basalam.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of cafebazaar.cloud/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of cafebazaar.cloud/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • cloud/DS (alg 8, id 49804): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cloud/DS (alg 8, id 49804): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cloud/DS (alg 8, id 49804): 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.
  • cloud/DS (alg 8, id 49804): 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.
  • basalam.com/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