Skip to content

Hostname

traderswebfx.jp

Last fetched

traderswebfx.jp resolves to 121.50.59.130, announced in 121.50.59.0/24 by SECOMTRUST - SECOM Trust Systems Co.,Ltd. in JP. traderswebfx.jp 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 · traderswebfx.jpRouting diversity2.4/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/traderswebfx.jp

Resolution chain

IPv6 resolution

No AAAA record for traderswebfx.jp is recorded in WhisperGraph.

Attribution

secom trust

ORIGIN_AS

WHOIS identity

Registrant organisation
t&c financial research,
Contact emails
tcfr.3832_ask@tandcfr.com, info@technowave.ad.jp

Subdomains

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

Mail and authentication

Nameservers

  • name.technowave.ad.jp
  • ns1.gslb4.sakura.ne.jp
  • ns2.gslb4.sakura.ne.jp
  • ns.technowave.ne.jp
  • 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

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: tc-spf.mrs.mpub.ne.jp

Threat-feed evidence

History

Related pages

Pivot from traderswebfx.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: "traderswebfx.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 20

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