All hostnames newsread.datafoundry.com resolves to 20 IPv4 addresses operated by GIGANEWS - Giganews, Inc. in US.
Nutrition Label WHISPER CANON · newsread.datafoundry.com Routing diversity 1.5/10 Peering density 3.1/10 MOAS conflict ✓ none Threat-feed listings 10.0/10 WHOIS transparency 0.0/10 Resolver footprint 4.6/10 canon.whisper.security/host/newsread.datafoundry.com Resolution chain newsread.datafoundry.com resolves to 20 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
IP Prefix ASN Operator Country 69.80.101.12 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.13 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.14 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.15 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.16 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.17 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.18 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.19 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.20 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.21 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.22 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.101.23 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.12 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.13 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.14 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.15 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.16 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.17 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.18 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US 69.80.102.19 69.80.96.0/21 AS30094 GIGANEWS - Giganews, Inc. US
WHOIS identity No WHOIS records are currently associated with newsread.datafoundry.com in WhisperGraph.
Related pages Pivot deeper into the graph from newsread.datafoundry.com.
Cypher and MCP Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "newsread.datafoundry.com"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server .