Skip to content

Hostname

bitcash.me

Last fetched

bitcash.me resolves to 203.174.69.173, announced in 203.174.64.0/20 by DATAHOTEL-JP - AS for DATAHOTEL, which is one of iDC in Japan, in JP. bitcash.me is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · bitcash.meRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/bitcash.me

Resolution chain

IPv6 resolution

No AAAA record for bitcash.me is recorded in WhisperGraph.

Attribution

nhn techorus

ORIGIN_AS

WHOIS identity

Registrar
iana:49
Registrant organisation
bitcash
Contact emails
media@bitcash.jp

Subdomains

Subdomain
develop.bitcash.me
m.bitcash.me
r20.bitcash.me
smtp.bitcash.me
stg.bitcash.me

Showing 5 of 5 subdomains (5 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

Sample outbound links

Mail and authentication

Nameservers

  • zns01.data-hotel.net
  • zns02.data-hotel.net

MX records

  • aspmx.l.google.com

Threat-feed evidence

History

Related pages

Pivot from bitcash.me 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: "bitcash.me"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.