Skip to content

Hostname

blog.danger.computer

Last fetched

blog.danger.computer resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.

Nutrition Label

WHISPER CANON · blog.danger.computerRouting diversity5.7/10Peering density9.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/blog.danger.computer

Resolution chain

blog.danger.computer resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
16.15.177.4316.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.183.1316.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.187.21416.15.184.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.199.2216.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.199.4316.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.199.5116.15.192.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.223.18716.15.216.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
52.216.34.2152.216.32.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.216.54.20552.216.48.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.17.16352.217.17.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.198.19752.217.192.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.229.18952.217.224.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.49.14752.217.49.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.85.1152.217.85.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.92.12352.217.92.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
54.231.197.7754.231.192.0/19AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

No WHOIS records are currently associated with blog.danger.computer in WhisperGraph.

Web-graph footprint

Distinct hostnames that link to or from blog.danger.computer in the public web crawl.

24 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Related pages

Pivot deeper into the graph from blog.danger.computer.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "blog.danger.computer"})-[: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.