Skip to content

Hostname

ronningen.ca

Last fetched

ronningen.ca resolves to 16 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists registrar:tucows.com co. as the registrar.

Nutrition Label

WHISPER CANON · ronningen.caRouting diversity5.2/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/ronningen.ca

Resolution chain

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

IPPrefixASNOperatorCountry
16.15.183.9116.15.176.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.223.19016.15.216.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.223.25316.15.216.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.15.223.3616.15.216.0/21AS14618AMAZON-AES - Amazon.com, Inc.US
16.182.104.6916.182.96.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
16.182.67.14116.182.64.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
16.182.73.13316.182.72.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
16.182.98.10116.182.96.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.216.212.19752.216.208.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.216.217.17352.216.208.0/20AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.172.18152.217.160.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.224.7752.217.224.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.230.19752.217.224.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.232.16552.217.224.0/19AS16509AMAZON-02 - Amazon.com, Inc.US
52.217.80.21152.217.80.0/24AS16509AMAZON-02 - Amazon.com, Inc.US
54.231.172.21354.231.160.0/19AS16509AMAZON-02 - Amazon.com, Inc.US

WHOIS identity

Registrar
registrar:tucows.com co.
Organization
Contact emails

Subdomains

2 observed subdomains of ronningen.ca.

Threat posture

History

Mail and authentication

SPF policy

1 SPF mechanism authorising senders for ronningen.ca.

MechanismTarget
SPF_INCLUDEspf.messagingengine.com

Related pages

Pivot deeper into the graph from ronningen.ca.

Cypher and MCP

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

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