chinamobileltd.com
Updated:
2021-06-07 20:57:35 UTC (1262 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- chinamobileltd.com/A
- chinamobileltd.com/NS
- chinamobileltd.com/SOA
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of chinamobileltd.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 54714)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to chinamobileltd.com
Secure (1)
- . to com
Notices
Errors (5)
- chinamobileltd.com zone: The following NS name(s) did not resolve to address(es): ns.chinamobileltd.com
- chinamobileltd.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (202.134.126.130)
- chinamobileltd.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.134.126.130, UDP_-_NOEDNS_)
- chinamobileltd.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.134.126.130, UDP_-_NOEDNS_)
- com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:503:231d::2:30)
Warnings (2)
- com to chinamobileltd.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns3.lofty.com.hk See RFC 1034, Sec. 4.2.2.
- com to chinamobileltd.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns.chinamobileltd.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
