View on GitHub

DNSViz: A DNS visualization tool

email.4-s.cloud

Updated: 2022-01-13 03:51:55 UTC (1486 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)
  • 4-s.cloud/A (NXDOMAIN)
  • email.4-s.cloud/A (NXDOMAIN)
Secure (1)
  • cloud/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of 4-s.cloud/A
  • NSEC3 proving non-existence of email.4-s.cloud/A
  • 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

Secure (1)
  • . to cloud

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of 4-s.cloud/A: 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 4-s.cloud/A: 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 email.4-s.cloud/A: 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 email.4-s.cloud/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • cloud/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • NSEC3 proving non-existence of 4-s.cloud/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of 4-s.cloud/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of email.4-s.cloud/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of email.4-s.cloud/A: 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.
  • cloud/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