Hostname
mytempdir.com
Last fetched
mytempdir.com resolves to 172.233.219.123, announced in 172.233.208.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. mytempdir.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:51:26 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 23:27:23 GMT
Nutrition Label
Resolution chain
- 172.233.219.123
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.49
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.233.219.78
172.233.208.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.25
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.38
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.237.146.8
172.237.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.193.161
172.239.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.234.27.37
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.234.27.71
172.234.16.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
No AAAA record for mytempdir.com is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- iana:472
- Registrant organisation
- andy chang
- Contact emails
- andy0126@hotmail.com, domainmanager@moniker.com, stvnwijaya@gmail.com, support@dropcatch.com
Subdomains
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.parklogic.com
- ns2.parklogic.com
MX records
- mx156.hostedmxserver.com
Threat-feed evidence
History
Related pages
Pivot from mytempdir.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: "mytempdir.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.