Skip to content

Hostname

ayva.cloud

Last fetched

ayva.cloud resolves to 23.173.208.164, announced in 23.173.208.0/24 by AYVA - Ayva in US. ayva.cloud 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 · ayva.cloudRouting diversity2.4/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/ayva.cloud

Resolution chain

IPv6 resolution

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:895
Registrant organisation
contact privacy inc. customer 7151571251
Contact emails
15f72891f29f30849abca0dd0d913ab8-7468075@contact.gandi.net

Subdomains

Subdomain
c2.ayva.cloud
ec2.ayva.cloud
rdns.ayva.cloud
uisp.ayva.cloud
ws-az-dc1.ayva.cloud
ws-dc1.ayva.cloud
ws-dc2.ayva.cloud

Showing 7 of 1,031. View all subdomains →

Mail and authentication

Nameservers

  • ws-az-dc1.ayva.cloud
  • ws-dc1.ayva.cloud
  • ws-dc2.ayva.cloud
  • 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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • a: ayva.cloud
  • include: _spf.google.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from ayva.cloud 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: "ayva.cloud"})-[: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.