Skip to content

Hostname

fluidair.com

Last fetched

fluidair.com resolves to 40.122.43.166, announced in 40.120.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. fluidair.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 · fluidair.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/fluidair.com

Resolution chain

IPv6 resolution

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

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
fluid-air products
Contact emails
info@fluidair.com, a8e0e1f7f5a540559df8a6d211030f0f.protect@withheldforprivacy.com

Subdomains

Subdomain
api.fluidair.com
cpanel.fluidair.com
cpcalendars.fluidair.com
cpcontacts.fluidair.com
fluidnt.fluidair.com
p21.fluidair.com
p21api.fluidair.com
p21play.fluidair.com
webdisk.fluidair.com
wildcard.fluidair.com
www.fluidair.com

Showing 11 of 11 subdomains (11 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

Mail and authentication

Nameservers

  • angela.ns.cloudflare.com
  • greg.ns.cloudflare.com
  • 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

  • kcxec1n4.computerstlouis.com
  • stlxec1n3.computerstlouis.com

SPF policy

  • include: spf.computerstlouis.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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