Skip to content

Hostname

atana.co.ke

Last fetched

atana.co.ke resolves to 104.21.20.206, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. atana.co.ke 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 · atana.co.keRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/atana.co.ke

Resolution chain

IPv6 resolution

Attribution

inmotion

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:kwe holding limited
Registrant organisation
ilani concepts

Subdomains

Subdomain
5e749bbb7abc.atana.co.ke
cpanel.atana.co.ke
cpcalendars.atana.co.ke
cpcontacts.atana.co.ke
mail.atana.co.ke
ns1.atana.co.ke
ns2.atana.co.ke
server.atana.co.ke
webdisk.atana.co.ke
webmail.atana.co.ke
whm.atana.co.ke
www.atana.co.ke

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

  • john.ns.cloudflare.com
  • tegan.ns.cloudflare.com
  • ns1.inmotionhosting.com
  • ns2.inmotionhosting.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

MX records

  • atana.co.ke
  • _dc-mx.5e749bbb7abc.atana.co.ke

SPF policy

  • include: smtp.servconfig.com
  • a: atana.co.ke
  • mx: atana.co.ke
  • ip: 162.144.76.162
  • ip: 173.231.244.183
  • ip: 192.145.239.210
  • ip: 198.46.87.160

Threat-feed evidence

History

Related pages

Pivot from atana.co.ke 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: "atana.co.ke"})-[: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.