Skip to content

Hostname

ozzy-match.com

Last fetched

ozzy-match.com resolves to 35.190.113.89, announced in 35.190.0.0/16 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. ozzy-match.com 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 · ozzy-match.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/ozzy-match.com

Resolution chain

IPv6 resolution

No AAAA record for ozzy-match.com is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
advanced digital services b.v.
Contact emails
02d9e1f0f6@ozzy-match.com.whoistrustee.com, info@domain-contact.org, 138b44b2f46ee7a2e8bad8946ea08d1ffce13a35839bf93c7760e8210d165523@ozzy-match.com.whoisproxy.org, 14f8ecc300209f59d8f5540cf9219cdace696cd1bc3234d4886692c1ae42afc3@ozzy-match.com.whoisproxy.org, 661ed22aa3933f13aabc0904c45c45ea3a91216fd9a03c4db8e3c87442180a5d@ozzy-match.com.whoisproxy.org, e6b6b578e3ebb4e51f811913c41008f3c31b9d6e8aa452667f4ee2962097e84f@ozzy-match.com.whoisproxy.org

Subdomains

Mail and authentication

Nameservers

  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns2.dnsimple-edge.net
  • 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
  • ns4.dnsimple-edge.org

MX records

  • mx1.fiercebadger.com

SPF policy

  • include: spf.fiekabln.com
  • include: md02.com
  • include: 136224628.spf2.netcorecloud.net

Threat-feed evidence

History

Related pages

Pivot from ozzy-match.com 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: "ozzy-match.com"})-[: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.