Skip to content

Hostname

vivonet.com

Last fetched

vivonet.com resolves to 100.22.75.208, announced in 101.10.68.0/22 by AMAZON-02 - Amazon.com, Inc. in US. vivonet.com 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 · vivonet.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/vivonet.com

Resolution chain

IPv6 resolution

No AAAA record for vivonet.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:269
Registrant organisation
farshad hadei
Contact emails
contact_it@vivonet.com, rltgknyojajg@idp.email, info@domain-contact.org

Subdomains

Subdomain
admin-ordernow.vivonet.com
audit.vivonet.com
beta.vivonet.com
cuda.vivonet.com
dds-a.vivonet.com
dds-b.vivonet.com
ddsync.vivonet.com
developer.vivonet.com
em3.vivonet.com
ih.vivonet.com
images.vivonet.com
implementation.vivonet.com

Showing 12 of 36. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-315.awsdns-39.com
  • ns-618.awsdns-13.net
  • ns-1131.awsdns-13.org
  • ns-2019.awsdns-60.co.uk

MX records

  • mx1.hc3692-74.iphmx.com
  • mx2.hc3692-74.iphmx.com

SPF policy

  • exists: %{i}.spf.hc3692-74.iphmx.com
  • include: mailsenders.netsuite.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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

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