Skip to content

Hostname

aishare.chat

Last fetched

aishare.chat resolves to 20 IPv4 addresses operated by AS402506 in HK.

Nutrition Label

WHISPER CANON · aishare.chatRouting diversity5.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/aishare.chat

Resolution chain

aishare.chat resolves to 20 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
149.88.90.146149.88.90.0/23AS402506—HK
149.88.90.238149.88.90.0/23AS402506—HK
149.88.90.9149.88.90.0/23AS402506—HK
15.204.104.6915.204.0.0/17AS16276—US
154.201.72.170154.201.72.0/23AS402506—HK
156.238.250.14156.238.250.0/23AS402506—HK
38.148.240.11038.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.11838.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.13738.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.14538.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.16738.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.19038.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.23938.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.5738.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.8238.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.148.240.9538.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.247.12.18938.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.247.13.17638.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.247.14.17538.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS
38.247.15.17538.0.0.0/8AS174COGENT-174 - Cogent Communications, LLCUS

WHOIS identity

No WHOIS records are currently associated with aishare.chat in WhisperGraph.

Subdomains

1 observed subdomain of aishare.chat.

Subdomain
static.aishare.chat

Threat posture

History

Related pages

Pivot deeper into the graph from aishare.chat.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "aishare.chat"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

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