Registered 20 years ago, no valid HTTPS certificate, the site did not answer (OSError).
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
| NS | 02.dnsv.jp 01.dnsv.jp 03.dnsv.jp 04.dnsv.jp |
|---|---|
| TXT | _globalsign-domain-verification=H_DMW987qtq0jdIhPRhkoex_Q3OgagjTPrKbNxBsNB v=spf1 ip4:150.95.10.64/28 ip4:210.157.2.0/29 ip4:210.157.2.8/29 ip4:210.157.2.16/29 -all |
| registered | 2006-11-10 |
|---|---|
| expires | 2026-11-30 |
| last changed | 2025-12-01 |
| owner | GMO Internet , Inc. |
| nameservers | 01.dnsv.jp 02.dnsv.jp 03.dnsv.jp 04.dnsv.jp |
| status | Active |
| valid | no |
|---|---|
| problem | Could not resolve host (ENODATA) |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 ip4:150.95.10.64/28 ip4:210.157.2.0/29 ip4:210.157.2.8/29 ip4:210.157.2.16/29 -all |
|---|---|
| DMARC | pass policy quarantine |
| 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 dnsv.jp.
Reference: /llms.txt.
IPv6. Does dnsv.jp work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch dnsv.jp. 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