Registered 6 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 434 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 172.67.74.156 104.26.8.104 104.26.9.104 |
|---|---|
| AAAA | 2606:4700:20::681a:868 2606:4700:20::681a:968 2606:4700:20::ac43:4a9c |
| NS | ines.ns.cloudflare.com cameron.ns.cloudflare.com |
| TXT | google-site-verification=Eo3NBGAnOXRT30uuGLbvG8xQZk_oTny97EPAIHY-QnQ |
| registrar | Cloudflare, Inc |
|---|---|
| registered | 2020-07-24 |
| expires | 2027-07-24 |
| last changed | 2026-08-13 |
| nameservers | ines.ns.cloudflare.com cameron.ns.cloudflare.com |
| status | client transfer prohibited |
| valid | yes |
|---|---|
| issuer | Google Trust Services |
| covers | hanime1.me, *.hanime1.me |
| protocol | TLSv1.3 |
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 hanime1.me.
Reference: /llms.txt.
IPv6. Does hanime1.me work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch hanime1.me. 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