Registered 32 years ago, no valid HTTPS certificate, the site did not answer (OSError).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| NS | ns01.trs-dns.com ns01.trs-dns.net ns10.trs-dns.org ns10.trs-dns.info |
|---|
| registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
|---|---|
| registered | 1994-10-26 |
| expires | 2035-10-25 |
| last changed | 2026-04-02 |
| nameservers | ns01.trs-dns.com ns01.trs-dns.net ns10.trs-dns.info ns10.trs-dns.org |
| status | client transfer prohibited |
| valid | no |
|---|---|
| problem | Could not resolve host (ENODATA) |
Domain is properly signed — chain validated by an independent validating resolver
| 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 in.net.
Reference: /llms.txt.
IPv6. Does in.net work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch in.net. 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