Skip to content

Hostname

ciklet.net.tr

Last fetched

ciklet.net.tr resolves to 213.238.162.212, announced in 213.238.162.0/24 by intibu - Ciklet Tasarim Iletisim ve Org. Tic. Ltd. Sti. in TR. ciklet.net.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 · ciklet.net.trRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/ciklet.net.tr

Resolution chain

IPv6 resolution

No AAAA record for ciklet.net.tr is recorded in WhisperGraph.

Attribution

ciklet tasarim iletisim ve org tic sti

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ciklet.net.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
autodiscover.ciklet.net.tr
btw.ciklet.net.tr
cdn.ciklet.net.tr
cloudpbx.ciklet.net.tr
dns.ciklet.net.tr
fr.ciklet.net.tr
ip.ciklet.net.tr
korumail.ciklet.net.tr
lg.ciklet.net.tr
lin01.ciklet.net.tr
mail.ciklet.net.tr
mailgate.ciklet.net.tr

Showing 12 of 1,491. View all subdomains →

Mail and authentication

Nameservers

  • 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
  • ns1.ciklet.net.tr
  • ns2.ciklet.net.tr
  • ns3.ciklet.net.tr
  • ns4.ciklet.net.tr

MX records

  • antispam.intibu.com

SPF policy

  • a: ciklet.net.tr
  • mx: ciklet.net.tr
  • a: mail.ciklet.net.tr
  • ip: 213.238.165.14

Threat-feed evidence

History

Related pages

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