Hostname
ok.com.tr
Last fetched
ok.com.tr resolves to 93.91.76.165, announced in 93.91.76.0/24 by ECZ-NET - Eczacibasi Bilisim San.ve Tic. A.S. in TR. ok.com.tr is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 93.91.76.165
93.91.76.0/24 · ECZ-NET - Eczacibasi Bilisim San.ve Tic. A.S. · Beşiktaş, TR
IPv6 resolution
No AAAA record for ok.com.tr is recorded in WhisperGraph.
Attribution
eczacibasi bilisim san ve tic
ORIGIN_AS
WHOIS identity
- Registrant organisation
- eip eczacyba?y ylac pazarlama a.?.
- Contact emails
- orhane@eczacibasi.com.tr
Subdomains
Showing 5 of 5 subdomains (5 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.
Mail and authentication
Nameservers
- ns01.eczacibasiebi.com
- ns02.eczacibasiebi.com
- ns03.eczacibasiebi.com
- 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
- ns01.eczacibasiebi.com.tr
- ns02.eczacibasiebi.com.tr
- ns03.eczacibasiebi.com.tr
MX records
- edge01.eczacibasi.com.tr
- edge02.eczacibasi.com.tr
- edge03.eczacibasi.com.tr
- edge04.eczacibasi.com.tr
- mail01.eczacibasi.com.tr
- mail02.eczacibasi.com.tr
- mail03.eczacibasi.com.tr
- mail04.eczacibasi.com.tr
- postman.eczacibasi.com.tr
- postman0.eczacibasi.com.tr
- postman1.eczacibasi.com.tr
- postman2.eczacibasi.com.tr
- postman3.eczacibasi.com.tr
SPF policy
- ip: 93.91.72.0/24
- ip: 93.91.74.0/24
- include: spf.mandrillapp.com
- include: mktomail.com
- include: spf.protection.outlook.com
- exists: %{i}._spf.e.sparkpost.com
- include: servers.mcsv.net
Threat-feed evidence
History
Related pages
Pivot from ok.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: "ok.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.