Skip to content

Hostname

fileforce.jp

Last fetched

fileforce.jp resolves to 13.227.192.101, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. fileforce.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 · fileforce.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint4.6/10canon.whisper.security/host/fileforce.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
whois privacy protection service by onamae.com
Contact emails
proxy@whoisprotectservice.com

Subdomains

Subdomain
a2h.fileforce.jp
api2.fileforce.jp
app.fileforce.jp
datacatalog.fileforce.jp
dev-gitlab.fileforce.jp
dev-hg.fileforce.jp
dev-hub.fileforce.jp
dev-mail.fileforce.jp
dev-matter.fileforce.jp
dev-npm.fileforce.jp
dev-nuget.fileforce.jp
dev-teamcity.fileforce.jp

Showing 12 of 58. View all subdomains →

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

  • ns-159.awsdns-19.com
  • ns-841.awsdns-41.net
  • ns-1478.awsdns-56.org
  • ns-1568.awsdns-04.co.uk

MX records

  • fileforce-jp.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: mail.zendesk.com
  • include: spf.bserver.jp
  • include: zcsend.net

Threat-feed evidence

History

Related pages

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