sina.cn
Updated:
2024-03-14 03:16:36 UTC (252 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- sina.cn/A
- sina.cn/MX
- sina.cn/NS
- sina.cn/SOA
- sina.cn/TXT
Secure (2)
- cn/SOA
- cn/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- 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 status
Insecure (1)
- cn to sina.cn
Secure (1)
- . to cn
Notices
Errors (3)
- 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.
- sina.cn/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- . 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, 202.112.0.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.
- sina.cn/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
