Skip to content

Hostname

computerjazz.com.au

Last fetched

computerjazz.com.au resolves to 103.209.24.129, announced in 103.209.24.0/23 by ARKTISMAPTYLTD-AS-AP - Arktisma Pty Ltd in AU. computerjazz.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 · computerjazz.com.auRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/computerjazz.com.au

Resolution chain

IPv6 resolution

IPv6 resolution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

Registrar
registrar:synergy wholesale accreditations pty ltd
Registrant organisation
general manager

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • ns1.serversaurus.com
  • ns2.serversaurus.com
  • ns3.serversaurus.com
  • ns4.serversaurus.com
  • 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

  • computerjazz.com.au

SPF policy

  • a: computerjazz.com.au
  • mx: computerjazz.com.au
  • include: _spf.serversaurus.com.au
  • ip: 103.209.24.129
  • ip: 202.130.34.75

Threat-feed evidence

History

Related pages

Pivot from computerjazz.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: "computerjazz.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.