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

| A | 104.155.197.197 |
|---|---|
| NS | 02.dnsv.jp 01.dnsv.jp 03.dnsv.jp 04.dnsv.jp |
| TXT | v=spf1 include:_spf.google.com include:mailgun.org ~all google-site-verification=Y0QtCzGI8c2NqwCTKLFU6KOQa5mm1kLun96E-TNK3qc |
| registered | 2011-03-02 |
|---|---|
| expires | 2027-03-31 |
| last changed | 2026-08-25 |
| owner | Cross Marketing, Inc. |
| nameservers | 01.dnsv.jp 02.dnsv.jp 03.dnsv.jp 04.dnsv.jp |
| status | Active |
| valid | yes |
|---|---|
| issuer | DigiCert Inc |
| covers | *.rsch.jp, rsch.jp |
| protocol | TLSv1.2 |
Domain is not signed with DNSSEC
| SPF | pass v=spf1 include:_spf.google.com include:mailgun.org ~all |
|---|---|
| DMARC | none |
| DKIM | found: mx |
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 rsch.jp.
Reference: /llms.txt.
IPv6. Does rsch.jp work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch rsch.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