Hostname
v4km.net
Last fetched
v4km.net resolves to 100.52.60.135, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. v4km.net 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
- 100.52.60.135
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 13.112.31.62
- 13.192.40.204
- 174.129.152.167
174.129.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.177.78.5
- 23.22.13.53
23.22.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.0.213.201
52.0.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.68.212.207
- 54.199.101.73
- 57.182.18.89
IPv6 resolution
No AAAA record for v4km.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- domain registration
- Contact emails
- domreg@impact.com, owner-363795@v4km.net.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| 41149.v4km.net |
| wildcard.v4km.net |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-105.awsdns-13.com
- ns-785.awsdns-34.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1114.awsdns-11.org
- ns-1959.awsdns-52.co.uk
Threat-feed evidence
History
Related pages
Pivot from v4km.net 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: "v4km.net"})-[: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.