Skip to content

Hostname

file.com.tr

Last fetched

file.com.tr resolves to 77.81.186.37, announced in 77.81.186.0/23 by FixCloud - FixCloud Teknoloji A.S. in TR. file.com.tr 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 · file.com.trRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/file.com.tr

Resolution chain

IPv6 resolution

No AAAA record for file.com.tr is recorded in WhisperGraph.

Attribution

fixcloud teknoloji

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for file.com.tr. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
arsiv.file.com.tr
dnsadmin.file.com.tr
earsiv.file.com.tr
f088_file_test.file.com.tr
management.file.com.tr
market.file.com.tr
www.file.com.tr

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

  • brenda.ns.cloudflare.com
  • lou.ns.cloudflare.com
  • dnsa1.vodafone.net.tr
  • dnsa2.vodafone.net.tr
  • dnx1.vodafone.net.tr
  • dnx2.vodafone.net.tr

MX records

  • cust38826-1.in.mailcontrol.com
  • cust38826-2.in.mailcontrol.com
  • mail.bim.com.tr
  • mail2.bim.com.tr

SPF policy

  • ip: 212.175.46.0/24
  • include: spf.protection.outlook.com
  • include: spf.bim.com.tr

Threat-feed evidence

History

Related pages

Pivot from file.com.tr 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: "file.com.tr"})-[: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.