View on GitHub

DNSViz: A DNS visualization tool

sina.cn

« 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 (5)
  • sina.cn/A
  • sina.cn/MX
  • sina.cn/NS
  • sina.cn/SOA
  • sina.cn/TXT
Secure (5)
  • cn/SOA
  • cn/SOA
  • cn/SOA
  • cn/SOA
  • cn/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • NSEC3 proving non-existence of sina.cn/DS
  • cn/DNSKEY (alg 8, id 38388)
  • cn/DNSKEY (alg 8, id 57724)
  • cn/DS (alg 8, id 57724)

Delegation statusDelegation status

Insecure (1)
  • cn to sina.cn
Secure (1)
  • . to cn

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of sina.cn/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 sina.cn/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • cn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (203.119.27.1)
  • cn/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (66.198.183.65, UDP_-_EDNS0_512_D_K)
  • sina.cn/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • . to cn: Authoritative AAAA records exist for ns.cernet.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • . to cn: The glue address(es) for ns.cernet.net (202.112.0.44) differed from its authoritative address(es) (103.137.60.44). See RFC 1034, Sec. 4.2.2.
  • NSEC3 proving non-existence of sina.cn/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sina.cn/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • cn to sina.cn: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the cn zone): ns1.sina.com.cn See RFC 1034, Sec. 4.2.2.
  • cn/DNSKEY (alg 8, id 38388): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (66.198.183.65, UDP_-_EDNS0_4096_D_K)
  • cn/DNSKEY (alg 8, id 57724): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (66.198.183.65, UDP_-_EDNS0_4096_D_K)
  • sina.cn/DS 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