Hostname
bokenya.jp
Last fetched
bokenya.jp is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. bokenya.jp is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
No IPv4 resolution is recorded for bokenya.jp in WhisperGraph.
IPv6 resolution
No AAAA record for bokenya.jp is recorded in WhisperGraph.
WHOIS identity
- Registrant organisation
- digitaladventure,inc.
- Contact emails
- system@digiadv.co.jp, iijima@dracon.jp, numazawa@dragoncontents.jp
Subdomains
| Subdomain |
|---|
| adm.bokenya.jp |
| isp.bokenya.jp |
| mail.bokenya.jp |
| ns.bokenya.jp |
| ns2.bokenya.jp |
| sp.bokenya.jp |
| sv01.bokenya.jp |
| sv03.bokenya.jp |
| sv04.bokenya.jp |
| www.bokenya.jp |
Showing 10 of 10 subdomains (10 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-184.awsdns-23.com
- ns1.svshost.com
- ns2.svshost.com
- ns-886.awsdns-46.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1119.awsdns-11.org
- ns-1634.awsdns-12.co.uk
MX records
- mail.bokenya.jp
SPF policy
- ip: 103.217.136.0/23
- ip: 115.166.145.0/24
- ip: 143.198.101.120
- ip: 153.120.65.131
- ip: 24.144.80.216
- ip: 64.23.181.163
Threat-feed evidence
History
Related pages
Pivot from bokenya.jp into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bokenya.jp"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.