Skip to content

Hostname

ai-flow.net

Last fetched

ai-flow.net resolves to 108.138.128.10, announced in 108.138.128.0/22 by AMAZON-02 - Amazon.com, Inc. in US. ai-flow.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 · ai-flow.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/ai-flow.net

Resolution chain

IPv6 resolution

No AAAA record for ai-flow.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
ai flow
Contact emails
info@cashflowy.net, 5686bf69-e32f-418e-af47-97d774c990c6@identity-protect.org, 7c4b1705-9089-472b-b489-48d62a807a0a@identity-protect.org, b12ab090-2080-432f-af49-fb52f9a7d5e2@identity-protect.org, da7d4c82-85c1-4cf7-80cf-39dcc097f5ac@identity-protect.org

Subdomains

Subdomain
api.ai-flow.net
app.ai-flow.net
docs.ai-flow.net
test-app.ai-flow.net
www.ai-flow.net

Showing 5 of 5 subdomains (5 per page).

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-455.awsdns-56.com
  • ns-558.awsdns-05.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-1489.awsdns-58.org
  • ns-1949.awsdns-51.co.uk

MX records

  • pro3.mail.ovh.net

SPF policy

  • include: mx.ovh.com

Threat-feed evidence

History

Related pages

Pivot from ai-flow.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: "ai-flow.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.