Skip to content

Hostname

eca.com.tr

Last fetched

eca.com.tr resolves to 45.10.148.110, announced in 45.10.148.0/24 by CE2 - CE2 BILGI TEKNOLOJILERI TICARET LIMITED SIRKETI in TR. eca.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 · eca.com.trRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint9.5/10canon.whisper.security/host/eca.com.tr

Resolution chain

IPv6 resolution

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

Attribution

ce2 bilgi teknolojileri ticaret sirketi

ORIGIN_AS

WHOIS identity

Registrant organisation
e.c.a. pres dokum sanayi anonim ?irketi
Contact emails
fikret@eca.com.tr

Subdomains

Subdomain
akilli.eca.com.tr
etiket.eca.com.tr
global.eca.com.tr
www.eca.com.tr

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

  • ns1.cloudns.net
  • ns2.cloudns.net
  • ns3.cloudns.net
  • ns4.cloudns.net
  • pns1.cloudns.net
  • pns2.cloudns.net
  • pns3.cloudns.net
  • pns4.cloudns.net
  • pns5.cloudns.net
  • pns6.cloudns.net
  • pns7.cloudns.net
  • pns8.cloudns.net
  • pns9.cloudns.net
  • 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

  • eca-com-tr.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • ip: 176.88.41.101

Threat-feed evidence

History

Related pages

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