Hostname
kaflo.com
Last fetched
kaflo.com resolves to 172.233.219.123, announced in 172.236.224.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. kaflo.com is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:47 GMT
- Last seen on a feed
- Sat, 05 Sep 2026 23:33:39 GMT
Nutrition Label
Resolution chain
- 172.233.219.123
172.236.224.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.49
172.236.224.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.78
172.236.224.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.25
172.240.28.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.38
172.240.28.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.8
172.240.28.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.194.227
172.240.48.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.194.117
172.240.48.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.238.172.116
172.240.37.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.57.230
172.240.42.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.238.172.228
172.240.37.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.238.176.31
172.240.37.0/24 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
Attribution
akamai linode ap connected
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1659
- Registrant organisation
- domains by proxy,
- Contact emails
- 391130@privacy-link.com
Subdomains
Mail and authentication
Nameservers
- ns1.parklogic.com
- ns2.parklogic.com
MX records
- mx156.hostedmxserver.com
- mx1.emailsendhub.com
Threat-feed evidence
History
Related pages
Pivot from kaflo.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: "kaflo.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.