Hostname
createnergy.com.au
Last fetched
createnergy.com.au resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists registrar:melbourne it as the registrar.
Nutrition Label
Resolution chain
createnergy.com.au resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.27.216 | 104.21.16.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.169.196 | 172.67.160.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- registrar:melbourne it
- Organization
- hadi nahvi
- Contact emails
- —
Subdomains
1 observed subdomain of createnergy.com.au.
| Subdomain |
|---|
| www.createnergy.com.au |
Web-graph footprint
Distinct hostnames that link to or from createnergy.com.au in the public web crawl.
9 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
27 SPF mechanisms authorising senders for createnergy.com.au.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.sparkpostmail.com |
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | au._netblocks.mimecast.com |
| SPF_INCLUDE | deliverygateways.mastercard.com |
| SPF_INCLUDE | spf.mandrillapp.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 103.170.2.0/24 |
| SPF_IP | 103.170.2.151/32 |
| SPF_IP | 103.69.164.0/22 |
| SPF_IP | 118.127.20.128/25 |
| SPF_IP | 13.54.130.0/32 |
| SPF_IP | 172.246.8.161 |
| SPF_IP | 174.142.244.6 |
| SPF_IP | 18.200.192.158/32 |
| SPF_IP | 190.92.159.18 |
| SPF_IP | 203.39.156.133 |
| SPF_IP | 203.63.17.93/32 |
| SPF_IP | 210.9.99.178/32 |
| SPF_IP | 23.235.220.85 |
| SPF_IP | 3.105.94.134/32 |
| SPF_IP | 34.252.205.76/32 |
| SPF_IP | 52.19.235.69/32 |
| SPF_IP | 52.19.41.236/32 |
| SPF_IP | 54.206.1.219/32 |
| SPF_IP | 54.240.71.177/31 |
| SPF_IP | 54.252.191.67/32 |
| SPF_IP | 54.79.108.104/32 |
Related pages
Pivot deeper into the graph from createnergy.com.au.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "createnergy.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.