Skip to content

Hostname

criticalwatch.com

Last fetched

criticalwatch.com resolves to 16 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:81 as the registrar.

Nutrition Label

WHISPER CANON · criticalwatch.comRouting diversity5.7/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/criticalwatch.com

Resolution chain

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

IPPrefixASNOperatorCountry
3.5.78.2083.5.78.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
3.5.83.1233.5.83.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
3.5.84.153.5.84.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.218.132.7452.218.132.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.218.229.16252.218.229.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.218.249.25052.218.249.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.128.15552.92.128.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.148.9152.92.144.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.161.5152.92.160.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.202.19552.92.200.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.205.10752.92.200.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.205.1952.92.200.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.226.24352.92.224.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.239.4352.92.232.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.250.17952.92.248.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.92.251.352.92.248.0/21AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

Registrar
iana:81
Organization
alert logic
Contact emails

Subdomains

1 observed subdomain of criticalwatch.com.

Web-graph footprint

Distinct hostnames that link to or from criticalwatch.com in the public web crawl.

13 sites link to this hostname.

Sample outbound links

Threat posture

History

Related pages

Pivot deeper into the graph from criticalwatch.com.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "criticalwatch.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 20

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