Skip to content

Hostname

trinitypet.com.au

Last fetched

trinitypet.com.au resolves to 54.252.32.131, announced in 54.252.0.0/17 by AMAZON-02 - Amazon.com, Inc. in AU. trinitypet.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 · trinitypet.com.auRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.2/10canon.whisper.security/host/trinitypet.com.au

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:synergy wholesale accreditations pty ltd
Registrant organisation
tony de bondi

Subdomains

Subdomain
gate.trinitypet.com.au
mail.trinitypet.com.au
search.trinitypet.com.au
ts.trinitypet.com.au
www.trinitypet.com.au

Showing 5 of 5 subdomains (5 per page).

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

  • auth1.dns.iig.com.au
  • auth2.dns.iig.com.au
  • dns.iig-au.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

  • trinitypet-com-au.mail.protection.outlook.com

SPF policy

  • include: dayforcehcm.com
  • include: spf.protection.outlook.com
  • ip: 101.178.225.52
  • ip: 139.130.199.42
  • ip: 144.140.212.46
  • ip: 146.112.119.66
  • ip: 202.14.148.223
  • ip: 203.48.34.153
  • ip: 27.131.81.115

Threat-feed evidence

History

Related pages

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