No valid HTTPS certificate, the site did not answer (OSError).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| NS | ns4.ctdns.cn ns2.ctdns.cn ns3.ctdns.cn ns1.ctdns.cn |
|---|
| registrar | 阿里云计算有限公司(万网) |
|---|---|
| nameservers | ns4.ctdns.cn ns1.ctdns.cn ns2.ctdns.cn ns3.ctdns.cn |
| status | ok |
| valid | no |
|---|---|
| problem | Could not resolve host (ENODATA) |
Domain is not signed with DNSSEC
| SPF | none |
|---|---|
| DMARC | none |
| DKIM | none of 1 common selectors |
Whether mail claiming to be from this domain can be checked as genuine.
Green: clean. Red: listed. Grey: the list did not answer.
Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on ctdns.cn.
Reference: /llms.txt.
IPv6. Does ctdns.cn work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch ctdns.cn. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.
Watch — $1 / 30 days