Skip to content

Hostname

wnokta.com

Last fetched

wnokta.com resolves to 176.53.74.84, announced in 176.53.74.0/24 by RADORE - Radore Veri Merkezi Hizmetleri A.S. in TR. wnokta.com 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 · wnokta.comRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/wnokta.com

Resolution chain

IPv6 resolution

No AAAA record for wnokta.com is recorded in WhisperGraph.

Attribution

radore veri merkezi hizmetleri

ORIGIN_AS

WHOIS identity

Registrar
iana:1601
Registrant organisation
wnokta bilisim hizmetleri ltd. sti.
Contact emails
domain@apiname.com, domainnameapi@wnokta.com, contact@panelonline.net, contact@privacyprotect.org

Subdomains

Subdomain
bb.wnokta.com
canli.wnokta.com
cdn.wnokta.com
dev.wnokta.com
dosya.wnokta.com
dr1.wnokta.com
drdns1.wnokta.com
drmail1.wnokta.com
drvds1.wnokta.com
drwin1.wnokta.com
git.wnokta.com
mail.wnokta.com

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

  • 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.wnokta.com.tr
  • ns2.wnokta.com.tr

MX records

  • mail.wnokta.com

SPF policy

  • a: wnokta.com
  • mx: wnokta.com
  • a: server.wnokta.com
  • ip: 176.53.74.83
  • ip: 176.53.74.84

Threat-feed evidence

History

Related pages

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