Hostname
vm313.com
Last fetched
vm313.com resolves to 108.156.60.117, announced in 108.156.60.0/22 by AMAZON-02 - Amazon.com, Inc. in IE. vm313.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
- 108.156.60.117
108.156.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.156.60.31
108.156.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.156.60.32
108.156.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 108.156.60.97
108.156.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 18.238.55.123
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.16
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.18
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.55.94
18.238.55.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.166.96.33
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.48
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.53
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.91
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.174.46.21
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.50
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.92
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.174.46.98
3.174.46.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1923
- Registrant organisation
- domain administrator
- Contact emails
- pw-210fed6f04fb41bfd85534f925ce0566@privacyguardian.org
Mail and authentication
Nameservers
- jose.ns.cloudflare.com
- kinsley.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from vm313.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: "vm313.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.