Skip to content

Hostname

va-api.net

Last fetched

va-api.net is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. va-api.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · va-api.netRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/va-api.net

Resolution chain

No IPv4 resolution is recorded for va-api.net in WhisperGraph.

IPv6 resolution

No AAAA record for va-api.net is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
identity protection service
Contact emails
05ccc52e-d1f3-418a-94c9-7b2438909439@identity-protect.org, a2447c44-a9b4-41fe-9329-c4e36694c93a@identity-protect.org, bb7946a3-1697-4835-8a7f-b8da40a43c29@identity-protect.org, c801c535-fe04-4a20-88ed-e8562213ca68@identity-protect.org, c8fc9a23-0888-486f-bab2-5f820708e9b6@identity-protect.org, dbdff7b6-5ef2-4150-a754-7139b321ffb6@identity-protect.org, owner-4504742@va-api.net.whoisprivacyservice.org, owner-9016398@va-api.net.whoisprivacyservice.org, owner@va-api.net.whoisprivacyservice.org

Subdomains

Subdomain
line-gw.va-api.net
static-v1.va-api.net

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns-351.awsdns-43.com
  • ns-672.awsdns-20.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-1368.awsdns-43.org
  • ns-1806.awsdns-33.co.uk

Threat-feed evidence

History

Related pages

Pivot from va-api.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: "va-api.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.