Skip to content

Hostname

ozyme.fr

Last fetched

ozyme.fr resolves to 217.15.81.149, announced in 217.15.80.0/20 by ALPHALINK-AS - Alphalink SASU in FR. ozyme.fr 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 · ozyme.frRouting diversity2.4/10Peering density5.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/ozyme.fr

Resolution chain

IPv6 resolution

No AAAA record for ozyme.fr is recorded in WhisperGraph.

Attribution

alphalink sasu

ORIGIN_AS

WHOIS identity

Registrar
registrar:gandi
Registrant organisation
ozyme
Contact emails
5d74771888597ce04ff94f274be899f0-1846061@contact.gandi.net

Subdomains

Subdomain
autodiscover.ozyme.fr
bio.ozyme.fr
infobio.ozyme.fr
sts.ozyme.fr
www.ozyme.fr
yris.ozyme.fr

Showing 6 of 9. 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

Mail and authentication

Nameservers

  • ns-150-a.gandi.net
  • ns-175-b.gandi.net
  • ns-98-c.gandi.net
  • ns1.gandi.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

MX records

  • ozyme-fr.mail.protection.outlook.com

SPF policy

  • ip: 5.226.2.176/28
  • ip: 31.172.232.198/32
  • ip: 185.92.37.57/32
  • include: spf.protection.outlook.com
  • a: smtp-gw1.silae.fr
  • include: mailgun.org
  • ip: 217.15.81.149
  • ip: 77.159.171.146
  • ip: 89.83.119.17
  • ip: 89.83.119.21

Threat-feed evidence

History

Related pages

Pivot from ozyme.fr 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: "ozyme.fr"})-[: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.