Hostname
kihysoco.com
Last fetched
kihysoco.com resolves to 198.38.92.237, announced in 198.38.92.0/24 by WHG-LON - WHG Hosting Services Ltd in GB. kihysoco.com 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
- 198.38.92.237
198.38.92.0/24 · WHG-LON - WHG Hosting Services Ltd · London, GB
- 78.142.63.228
78.142.63.0/24 · TELEHOUSE-AS - Telehouse EAD · Sofia, BG
IPv6 resolution
No AAAA record for kihysoco.com is recorded in WhisperGraph.
Attribution
whg
MAIL_RECEIVER, ORIGIN_AS
WHOIS identity
- Registrar
- iana:303
- Registrant organisation
- john mutinda
- Contact emails
- mwaumutinda@gmail.com
Subdomains
| Subdomain |
|---|
| autodiscover.kihysoco.com |
| cpanel.kihysoco.com |
| cpcalendars.kihysoco.com |
| cpcontacts.kihysoco.com |
| mail.kihysoco.com |
| webdisk.kihysoco.com |
| webmail.kihysoco.com |
| www.kihysoco.com |
Showing 8 of 8 subdomains (8 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
- ns1.mysecurecloudhost.com
- ns2.mysecurecloudhost.com
- ns3.mysecurecloudhost.com
- ns4.mysecurecloudhost.com
- ns415.kenyawebexperts.co.ke
- ns416.kenyawebexperts.co.ke
- 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
- kihysoco.com
SPF policy
- a: kihysoco.com
- mx: kihysoco.com
- include: spf.mysecurecloudhost.com
- ip: 198.38.92.237
- ip: 78.142.63.228
- ip: 91.148.168.109
Threat-feed evidence
History
Related pages
Pivot from kihysoco.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: "kihysoco.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.