Skip to content

Hostname

amtech.co.ke

Last fetched

amtech.co.ke resolves to 41.80.37.17, announced in 41.80.37.0/24 by Safaricom Limited - Safaricom Limited in KE. amtech.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 · amtech.co.keRouting diversity1.5/10Peering density6.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/amtech.co.ke

Resolution chain

IPv6 resolution

No AAAA record for amtech.co.ke is recorded in WhisperGraph.

Attribution

safaricom

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for amtech.co.ke. 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
autoconfig.amtech.co.ke
autodiscover.amtech.co.ke
certificate.amtech.co.ke
co-opapi.amtech.co.ke
co-opapitest.amtech.co.ke
cpanel.amtech.co.ke
cpcalendars.amtech.co.ke
cpcontacts.amtech.co.ke
easybima.amtech.co.ke
easyblockm.amtech.co.ke
easyblocksupport.amtech.co.ke
easysacco.amtech.co.ke

Showing 12 of 50. View all subdomains →

Mail and authentication

Nameservers

  • ns1.safaricombusiness.co.ke
  • ns2.safaricombusiness.co.ke
  • ns3.safaricombusiness.co.ke
  • ns4.safaricombusiness.co.ke

MX records

  • rat-01.safaricombusiness.co.ke
  • rat-02.safaricombusiness.co.ke
  • rat-03.safaricombusiness.co.ke
  • rat-04.safaricombusiness.co.ke
  • smtp01.safaricombusiness.co.ke
  • smtp02.safaricombusiness.co.ke

SPF policy

  • redirect: _spf.safaricombusiness.co.ke

Threat-feed evidence

History

Related pages

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