View on GitHub

DNSViz: A DNS visualization tool

_acme-challenge.app.sibroschina.tech

« 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)
  • _acme-challenge.app.sibroschina.tech/CNAME
  • f1812fa2-256a-4550-810c-cc4567b0f690.auth.sibroschina.tech/A (NODATA)
  • f1812fa2-256a-4550-810c-cc4567b0f690.auth.sibroschina.tech/AAAA (NODATA)
Secure (1)
  • tech/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of sibroschina.tech/DS
  • tech/DNSKEY (alg 8, id 1990)
  • tech/DNSKEY (alg 8, id 50095)
  • tech/DNSKEY (alg 8, id 63970)
  • tech/DS (alg 8, id 50095)
  • tech/DS (alg 8, id 50095)

Delegation statusDelegation status

Insecure (2)
  • sibroschina.tech to auth.sibroschina.tech
  • tech to sibroschina.tech
Secure (1)
  • . to tech

NoticesNotices

Errors (4)
  • auth.sibroschina.tech zone: There was an error resolving the following NS name(s) to address(es): auth.sibroschina.tech
  • auth.sibroschina.tech/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (183.253.57.210, 211.99.99.58, 218.98.111.140, UDP_-_NOEDNS_)
  • f1812fa2-256a-4550-810c-cc4567b0f690.auth.sibroschina.tech/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (183.253.57.210, 211.99.99.58, 218.98.111.140, UDP_-_EDNS0_4096_D_KN)
  • f1812fa2-256a-4550-810c-cc4567b0f690.auth.sibroschina.tech/AAAA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (183.253.57.210, 211.99.99.58, 218.98.111.140, UDP_-_EDNS0_4096_D_KN)
Warnings (9)
  • auth.sibroschina.tech zone: No IPv4 addresses were found for NS records in the parent or child zone.
  • sibroschina.tech to auth.sibroschina.tech: The following NS name(s) required glue, but no glue was returned in the referral: auth.sibroschina.tech See RFC 1034, Sec. 4.2.1.
  • sibroschina.tech to auth.sibroschina.tech: The following NS name(s) were found in the delegation NS RRset (i.e., in the sibroschina.tech zone), but not in the authoritative NS RRset: auth.sibroschina.tech See RFC 1034, Sec. 4.2.2.
  • tech to sibroschina.tech: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (194.169.218.60, 2a04:2b00:13ee::60, UDP_-_EDNS0_4096_D_KN)
  • tech/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (194.169.218.60, UDP_-_EDNS0_512_D_KN)
  • tech/DS (alg 8, id 50095): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tech/DS (alg 8, id 50095): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tech/DS (alg 8, id 50095): 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.
  • tech/DS (alg 8, id 50095): 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