Hostname
keren.mlktng.com
Last fetched
keren.mlktng.com resolves to 1 IPv4 address operated by NEXEON - Nexeon Technologies, Inc. in US.
Nutrition Label
Resolution chain
keren.mlktng.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 64.44.195.167 | 64.44.192.0/21 | AS20278 | NEXEON - Nexeon Technologies, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with keren.mlktng.com in WhisperGraph.
Subdomains
17 observed subdomains of keren.mlktng.com.
Threat posture
History
Mail and authentication
MX records
SPF policy
43 SPF mechanisms authorising senders for keren.mlktng.com.
| Mechanism | Target |
|---|---|
| SPF_IP | 192.227.127.222 |
| SPF_IP | 192.227.127.223 |
| SPF_IP | 192.227.127.224 |
| SPF_IP | 192.227.127.225 |
| SPF_IP | 192.227.127.226 |
| SPF_IP | 45.11.59.148 |
| SPF_IP | 45.11.59.168 |
| SPF_IP | 51.81.73.160 |
| SPF_IP | 51.81.73.161 |
| SPF_IP | 51.81.73.162 |
| SPF_IP | 51.81.73.163 |
| SPF_IP | 51.81.74.72 |
| SPF_IP | 51.81.74.73 |
| SPF_IP | 51.81.74.74 |
| SPF_IP | 51.81.74.75 |
| SPF_IP | 51.81.78.240 |
| SPF_IP | 51.81.78.242 |
| SPF_IP | 51.91.164.151 |
| SPF_IP | 51.91.164.152 |
| SPF_IP | 51.91.164.154 |
| SPF_IP | 51.91.36.93 |
| SPF_IP | 54.37.231.60 |
| SPF_IP | 64.235.41.174 |
| SPF_IP | 64.235.41.186 |
| SPF_IP | 64.235.41.193 |
| SPF_IP | 64.235.41.194 |
| SPF_IP | 70.32.0.107 |
| SPF_IP | 70.32.2.176 |
| SPF_IP | 70.32.2.177 |
| SPF_IP | 70.32.2.178 |
| SPF_IP | 70.32.2.179 |
| SPF_IP | 74.48.142.114 |
| SPF_IP | 74.48.142.115 |
| SPF_IP | 74.48.142.119 |
| SPF_IP | 74.48.142.120 |
| SPF_IP | 74.48.142.121 |
| SPF_IP | 82.192.80.176 |
| SPF_IP | 85.17.132.10 |
| SPF_IP | 85.17.132.8 |
| SPF_IP | 85.17.31.166 |
| SPF_IP | 85.17.31.179 |
| SPF_IP | 91.222.173.145 |
| SPF_IP | 91.222.173.163 |
Related pages
Pivot deeper into the graph from keren.mlktng.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "keren.mlktng.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.