Hostname
myatstudio.com
Last fetched
myatstudio.com resolves to 208.115.249.234, announced in 208.115.249.0/24 by LIMESTONENETWORKS - Limestone Networks, Inc. in US. myatstudio.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
- Tue, 22 Sep 2026 23:26:40 GMT
Nutrition Label
Resolution chain
- 208.115.249.234
208.115.249.0/24 · LIMESTONENETWORKS - Limestone Networks, Inc. · Helena, US
- 208.115.249.235
208.115.249.0/24 · LIMESTONENETWORKS - Limestone Networks, Inc. · Helena, US
- 212.92.104.116
212.92.104.0/21 · NFORCE - NForce Entertainment B.V. · Veldhoven, NL
- 212.92.104.118
212.92.104.0/21 · NFORCE - NForce Entertainment B.V. · Veldhoven, NL
- 212.92.104.120
212.92.104.0/21 · NFORCE - NForce Entertainment B.V. · Veldhoven, NL
- 212.92.104.122
212.92.104.0/21 · NFORCE - NForce Entertainment B.V. · Veldhoven, NL
- 212.92.104.123
212.92.104.0/21 · NFORCE - NForce Entertainment B.V. · Veldhoven, NL
- 37.48.77.81
37.48.64.0/18 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 37.48.77.83
37.48.64.0/18 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 5.79.75.212
5.79.64.0/18 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 64.31.3.230
64.31.3.0/24 · LIMESTONENETWORKS - Limestone Networks, Inc. · Salt Lake City, US
IPv6 resolution
No AAAA record for myatstudio.com is recorded in WhisperGraph.
Attribution
limestone
ORIGIN_AS
WHOIS identity
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- ns1.brainydns.com
- ns2.brainydns.com
- ns1.emu-dns.com
- ns1.kirklanddc.com
- ns2.kirklanddc.com
- ns1.koaladns.com
- ns2.koaladns.com
- ns1.magpiedns.com
- ns2.magpiedns.com
- ns1.squirreldns.com
Threat-feed evidence
History
Related pages
Pivot from myatstudio.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: "myatstudio.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.