Skip to content

Hostname

halenet.com.au

Last fetched

halenet.com.au resolves to 203.17.235.146, announced in 203.17.235.0/24 by EXETEL-AS-AP - Exetel Pty Ltd in AU. halenet.com.au is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · halenet.com.auRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.2/10canon.whisper.security/host/halenet.com.au

Resolution chain

IPv6 resolution

No AAAA record for halenet.com.au is recorded in WhisperGraph.

Attribution

superloop australia

ORIGIN_AS

WHOIS identity

Registrar
registrar:synergy wholesale accreditations pty ltd
Registrant organisation
tim mccullagh

Subdomains

Subdomain
10.halenet.com.au
100.halenet.com.au
101.halenet.com.au
102.halenet.com.au
103.halenet.com.au
104.halenet.com.au
105.halenet.com.au
106.halenet.com.au
107.halenet.com.au
108.halenet.com.au
109.halenet.com.au
11.halenet.com.au

Showing 12 of 920. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns3.halenet.com.au
  • ns4.halenet.com.au
  • ns2.shoalhaven.net.au
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • matilda.halenet.com.au

SPF policy

  • ip: 203.17.235.145/32
  • ip: 203.55.33.233/32
  • a: mail.halenet.com.au
  • mx: mail.halenet.com.au
  • a: matilda.halenet.com.au

Threat-feed evidence

History

Related pages

Pivot from halenet.com.au into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "halenet.com.au"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

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