Hostname
kangatech.com.au
Last fetched
kangatech.com.au resolves to 15 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
kangatech.com.au resolves to 15 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.5.77.164 | 3.5.77.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.80.35 | 3.5.80.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.81.197 | 3.5.81.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.81.217 | 3.5.81.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.84.3 | 3.5.84.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.5.85.12 | 3.5.85.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.132.66 | 52.218.132.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.181.186 | 52.218.181.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.218.182.58 | 52.218.182.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.128.91 | 52.92.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.130.147 | 52.92.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.165.99 | 52.92.160.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.178.91 | 52.92.176.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.213.51 | 52.92.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.92.225.67 | 52.92.224.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
No WHOIS records are currently associated with kangatech.com.au in WhisperGraph.
Subdomains
1 observed subdomain of kangatech.com.au.
| Subdomain |
|---|
| www.kangatech.com.au |
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for kangatech.com.au.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from kangatech.com.au.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "kangatech.com.au"})-[: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.