How is jra.jp?
Looks fine
risk 0/100
Registered 26 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 1021 ms.
Why
0 20 50 100
fine careful high risk
· Nothing in the checks added risk.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.
The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.
HTTPS
141 d
left on a DigiCert Inc certificate
Age
26 years
registered 2001-03-26
Blocklists
0
listings across 5 lists
Everything we looked at
DNS records 3 record types A 23.212.251.201 23.212.251.196 23.212.251.213 23.212.251.205 23.212.251.209 23.212.251.210 23.212.251.216 23.212.251.219 NS a26-67.akam.net a14-65.akam.net a16-66.akam.net a7-65.akam.net a1-94.akam.net a3-64.akam.net TXT jqrXuQ9upQ3FkzjCduALpDFEAJbc9V zLgGjTDje8nhlFNOc0PWSwXD1GVzUd _tgcw89lntcj9bmtedi7fmo3hz2ghxqe _guj05q7or5fofetkq55w4pomtj39f7l UF1LnsdiLuTLhoGKu7Ug29je7tPVk9 E4kuAC0kFnq30WfdbgdE27oO7UT6tI
Registration registrar not reported registered 2001-03-26 expires 2027-03-31 last changed 2026-04-01 owner The Japan Racing Association nameservers a1-94.akam.net a14-65.akam.net a16-66.akam.net a26-67.akam.net a3-64.akam.net a7-65.akam.net status Active
registered 2001-03-26 expires 2027-03-31
HTTPS certificate 141 days left valid yes issuer DigiCert Inc covers www.jra.go.jp, app.jra.jp, jra.jp, sp.jra.jp protocol TLSv1.3
issued 2026-09-03 expires 2027-03-20
DNSSEC insecure Domain is not signed with DNSSEC
. → jp → jra.jp
Email authentication poor SPF none DMARC none DKIM none of 1 common selectors
Whether mail claiming to be from this domain can be checked as genuine.
Security score grade D · 107/205 Basic Security
10/40 missing: DNSSEC Enabled, Nameserver Diversity Record Security
0/45 missing: CAA Records, SPF Record, DMARC Record, DKIM Presence Advanced Security
10/25 missing: Mail Server Configuration, IPv6 Support Domain Reputation
42/50 missing: Typosquatting Check Threat Detection
45/45 missing: Domain Age Check Blocklists 0 listings · 17 lookups SURBL Multidomain URIBL Multidomain SpamCop23.212.248.25 Barracuda23.212.248.25 UCEPROTECT Level 123.212.248.25 SpamCop23.212.248.23 Barracuda23.212.248.23 UCEPROTECT Level 123.212.248.23 SpamCop23.212.248.12 Barracuda23.212.248.12 UCEPROTECT Level 123.212.248.12 SpamCop23.212.248.22 Barracuda23.212.248.22 UCEPROTECT Level 123.212.248.22 SpamCop23.212.248.7 Barracuda23.212.248.7 UCEPROTECT Level 123.212.248.7
Green: clean. Red: listed. Grey: the list did not answer.
Ask it yourself
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.
curl "https://how.is/v1/domain/trust?domain=jra.jp" \
-H "Authorization: Bearer $HOWIS_KEY"
# or pay per call in USDC (x402), no key: the 402 tells your agent the price
curl -i "https://how.is/v1/domain/profile?domain=jra.jp"
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install ) and ask for domain_trust on jra.jp.
Reference: /llms.txt .
Watch jra.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
Checked 2026-10-30 11:10:08+00:00 UTC · saved result; checking it here yourself refreshes it ·
lookups by the dns.pizza engine · the verdict is rule-based on age, blocklists and
HTTPS: a heuristic, not a guarantee.