Skip to content

Hostname

fillo.com.tr

Last fetched

fillo.com.tr resolves to 104.26.4.61, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fillo.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 · fillo.com.trRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/fillo.com.tr

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fillo.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
filloportalnet.fillo.com.tr
filloweb.fillo.com.tr
filloweb2.fillo.com.tr
flys-test.fillo.com.tr
intranet.fillo.com.tr
mail.fillo.com.tr
mail2.fillo.com.tr
sube.fillo.com.tr
web.fillo.com.tr
webapi.fillo.com.tr
www.fillo.com.tr

Showing 11 of 12. 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

  • eleanor.ns.cloudflare.com
  • hal.ns.cloudflare.com
  • dnsa1.vodafone.net.tr
  • dnsa2.vodafone.net.tr
  • dnx1.vodafone.net.tr
  • dnx2.vodafone.net.tr

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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