View on GitHub

DNSViz: A DNS visualization tool

edu.cn

Updated: 2025-02-09 02:13:23 UTC (4 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

Secure (6)
  • edu.cn/CDNSKEY
  • edu.cn/CDS
  • edu.cn/NS
  • edu.cn/NSEC3PARAM
  • edu.cn/SOA
  • edu.cn/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26470)
  • ./DNSKEY (alg 8, id 38696)
  • cn/DNSKEY (alg 8, id 38388)
  • cn/DNSKEY (alg 8, id 57724)
  • cn/DS (alg 8, id 57724)
  • edu.cn/DNSKEY (alg 8, id 15397)
  • edu.cn/DNSKEY (alg 8, id 44583)
  • edu.cn/DS (alg 8, id 15397)
  • edu.cn/DS (alg 8, id 15397)

Delegation statusDelegation status

Secure (2)
  • . to cn
  • cn to edu.cn

NoticesNotices

Errors (5)
  • cn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:dc7:1::1)
  • edu.cn zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (166.111.8.30, 202.38.109.35, 2001:250:c006::35)
  • edu.cn/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (166.111.8.30, 202.38.109.35, 2001:250:c006::35, TCP_-_EDNS0_4096_D_N)
  • edu.cn/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • y18ux.gcnar.edu.cn/A 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, 202.112.0.44). See RFC 1034, Sec. 4.2.2.
  • edu.cn/CDS: The contents of the DS RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
  • edu.cn/DS (alg 8, id 15397): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • edu.cn/DS (alg 8, id 15397): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • edu.cn/DS (alg 8, id 15397): 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.
  • edu.cn/DS (alg 8, id 15397): 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.
  • edu.cn/SOA: 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. (202.38.109.35, UDP_-_EDNS0_4096_D_KN_0x20)

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