Skip to content

Hostname

criticallabs.com

Last fetched

criticallabs.com resolves to 15 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.

Nutrition Label

WHISPER CANON · criticallabs.comRouting diversityPeering densityMOAS conflictThreat-feed listingsWHOIS transparencyResolver footprintcanon.whisper.security/host/criticallabs.com

Resolution chain

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

IPPrefixASNOperatorCountry
13.58.106.18113.58.0.0/15AS16509AMAZON-02 - Amazon.com, Inc.US
18.188.164.6818.188.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
18.189.246.7418.189.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
18.190.226.4618.190.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
18.216.114.11518.216.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.US
18.216.57.5818.216.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.US
18.218.137.20318.216.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.US
18.225.124.12318.224.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.US
3.131.86.1303.131.0.0/16AS16509AMAZON-02 - Amazon.com, Inc.US
3.134.179.1423.132.0.0/14AS16509AMAZON-02 - Amazon.com, Inc.US
3.147.3.973.144.0.0/13AS16509AMAZON-02 - Amazon.com, Inc.US
3.148.156.1993.144.0.0/13AS16509AMAZON-02 - Amazon.com, Inc.US
3.148.25.1993.144.0.0/13AS16509AMAZON-02 - Amazon.com, Inc.US
3.149.76.1073.144.0.0/13AS16509AMAZON-02 - Amazon.com, Inc.US
16.58.121.23816.58.0.0/17AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

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

Threat posture

History

Mail and authentication

SPF policy

1 SPF mechanism authorising senders for criticallabs.com.

MechanismTarget
SPF_INCLUDEspf.protection.outlook.com

Related pages

Pivot deeper into the graph from criticallabs.com.

Cypher and MCP

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

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