View on GitHub

DNSViz: A DNS visualization tool

auth.coust.cloud

« 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 (1)
  • coust.cloud/SOA
Secure (1)
  • cloud/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of coust.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)

Delegation statusDelegation status

Lame (1)
  • coust.cloud to auth.coust.cloud
Insecure (1)
  • cloud to coust.cloud
Secure (1)
  • . to cloud

NoticesNotices

Errors (6)
  • NSEC3 proving non-existence of coust.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 coust.cloud/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • auth.coust.cloud zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (35.211.229.210)
  • auth.coust.cloud zone: There was an error resolving the following NS name(s) to address(es): auth.coust.cloud
  • auth.coust.cloud/A: The server was not reachable over UDP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (35.211.229.210, UDP_-_EDNS0_4096_D_KN)
  • auth.coust.cloud/NS: The server was not reachable over UDP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (35.211.229.210, UDP_-_EDNS0_4096_D_KN)
Warnings (6)
  • NSEC3 proving non-existence of coust.cloud/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of coust.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.

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