How is navitime.co.jp?
Looks fine
risk 0/100
Registered 27 years ago, on no blocklists we checked, valid HTTPS, the site answered 403 in 97 ms.
Why
02050100
finecarefulhigh 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.
Site
403
97 ms
HTTPS
195 d
left on a Amazon certificate
Age
27 years
registered 2000-03-10
Blocklists
0
listings across 5 lists
Everything we looked at
DNS records4 record types
| A | 18.165.83.126 18.165.83.76 18.165.83.58 18.165.83.11 |
|---|---|
| MX | 5 alt1.aspmx.l.google.com 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 20 aspmx3.googlemail.com |
| NS | ns-1708.awsdns-21.co.uk ns-869.awsdns-44.net ns-1071.awsdns-05.org ns-323.awsdns-40.com |
| TXT | anthropic-domain-verification-sxmjgm=xrUkVeUUzGmqm6lVPNLEncYNz google-site-verification=IS1Lc4tmXKjchh9El8AJs_j6A1vfzdULBr9Qi72CMUg MS=ms88767435 notion_verify_Ayyfz~1GmRwMFp_2uZJ+nFuzrjFf*LYqRih7T:LxsZ.Uf)nHQd3fiTYp9>iB heyhack-verification=2f9fda1d-bfa2-4f0e-bcc7-4ef4293c819d facebook-domain-verification=jbzmobjkkdbsvfvzvtw4vgc7fcktdh openai-domain-verification=dv-IrzDmyIB6tK2Dr8y7b4EZLf0 3zyrz2khb5mwccn6c1b25g4j04cvxx4j SFMC-cifT4J7ZWTrpR0maWrMRo0QUwIyl1U-1dV3KXmaf adobe-idp-site-verification=7fbee29734cd08c66031d10195934f5739a1abc141e216fe9488d2de625e8aa6 zapier-domain-verification-challenge=aeb3de7c-e797-4867-8ef3-89a0f799b243 google-site-verification=zGy-KIXJF_V9PjFlzP99euM0XovblnH32Fv3cfS1nIg atlassian-domain-verification=N6NI7s4mqadluwv5jSZ/ZneUUybwATiHGM6lmSudQrtfFrv7jJTPkaZXOTsZURLO v=spf1 include:_spf.google.com include:spf.smktg.jp include:amazonses.com include:21230802.spf08.hubspotemail.net a:smartat.jp ip4:220.213.236.128/28 +ip4:220.213.230.96/28 +ip4:113.157.235.192/26 +ip4:61.123.211.16/28 +ip4:52.199.178.160 +ip4:52.199.30.248 +ip4:52.68.50.178 ~all |
Registrationregistrar not reported
| registered | 2000-03-10 |
|---|---|
| expires | 2027-03-31 |
| last changed | 2026-04-01 |
| owner | NAVITIME JAPAN CO., LTD. |
| nameservers | ns-869.awsdns-44.net ns-1071.awsdns-05.org ns-1708.awsdns-21.co.uk ns-323.awsdns-40.com |
| status | Connected (2027/03/31) |
registered 2000-03-10expires 2027-03-31
HTTPS certificate195 days left
| valid | yes |
|---|---|
| issuer | Amazon |
| covers | navitime.co.jp |
| protocol | TLSv1.3 |
issued 2026-10-27expires 2027-05-12
DNSSECinsecure
Domain is not signed with DNSSEC
. → jp → co.jp → navitime.co.jp
Email authenticationgood
| SPF | pass v=spf1 include:_spf.google.com include:spf.smktg.jp include:amazonses.com include:21230802.spf08.hubspotemail.net a:smartat.jp ip4:220.213.236.128/28 +ip4:220.213.230.96/28 +ip4:113.157.235.192/26 +ip4:61.123.211.16/28 +ip4:52.199.178.160 +ip4:52.199.30.248 +ip4:52.68.50.178 ~all |
|---|---|
| DMARC | warning policy none |
| DKIM | found: default, google |
Whether mail claiming to be from this domain can be checked as genuine.
Security scoregrade B · 158/205
Basic Security20/40missing: DNSSEC Enabled
Record Security23/45missing: CAA Records, DMARC Record, DKIM Presence
Advanced Security20/25missing: IPv6 Support
Domain Reputation50/50
Threat Detection45/45missing: Domain Age Check
Blocklists0 listings · 14 lookups
SURBL MultidomainURIBL MultidomainSpamCop18.165.83.58Barracuda18.165.83.58UCEPROTECT Level 118.165.83.58SpamCop18.165.83.126Barracuda18.165.83.126UCEPROTECT Level 118.165.83.126SpamCop18.165.83.11Barracuda18.165.83.11UCEPROTECT Level 118.165.83.11SpamCop18.165.83.76Barracuda18.165.83.76UCEPROTECT Level 118.165.83.76
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=navitime.co.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=navitime.co.jp"
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on navitime.co.jp.
Reference: /llms.txt.
Watch navitime.co.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