Skip to content

Hostname

bin.jvnv.net

Last fetched

bin.jvnv.net resolves to 109.74.192.157, announced in 109.74.192.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in GB. bin.jvnv.net is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:55:39 GMT
Last seen on a feed
Wed, 16 Sep 2026 20:18:23 GMT

Nutrition Label

WHISPER CANON · bin.jvnv.netRouting diversity1.5/10Peering density6.3/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/bin.jvnv.net

Resolution chain

IPv6 resolution

Attribution

akamai

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bin.jvnv.net. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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.jvnv.net
  • ns2.jvnv.net
  • ns3.jvnv.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

MX records

  • nagisa.jvnv.net

SPF policy

  • a: bin.jvnv.net

Threat-feed evidence

History

Related pages

Pivot from bin.jvnv.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: "bin.jvnv.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.