Skip to content

Hostname

ozio.jp

Last fetched

ozio.jp resolves to 184.150.70.120, announced in 184.150.64.0/19 by BACOM - Bell Canada in CA. ozio.jp 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 · ozio.jpRouting diversity2.4/10Peering density9.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint5.6/10canon.whisper.security/host/ozio.jp

Resolution chain

IPv6 resolution

No AAAA record for ozio.jp is recorded in WhisperGraph.

Attribution

bell canada

ORIGIN_AS

WHOIS identity

Registrant organisation
ozio co. ,ltd
Contact emails
hayato-yoshii@belluna.co.jp, ml40_unyo_domain-ssl@belluna.co.jp

Subdomains

Subdomain
cmspv.ozio.jp
cp.ozio.jp
dev-cmspv.ozio.jp
dev-ecmail.ozio.jp
dev-rehe.ozio.jp
dev.ozio.jp
ebis.ozio.jp
ecmail01.ozio.jp
ecmail02.ozio.jp
email.ozio.jp
gtm.ozio.jp
im-origin-9936312fa96c0de18f3229d5553b6f94.ozio.jp

Showing 12 of 20. 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

  • a1-235.akam.net
  • a11-64.akam.net
  • a18-64.akam.net
  • a20-65.akam.net
  • a4-65.akam.net
  • a9-67.akam.net

MX records

  • mailgwnr.oneoffice.jp
  • ozio-jp.in.tmems-jp.trendmicro.com

SPF policy

  • include: spf.bserver.jp
  • include: spf-bma.mpme.jp
  • include: scorpio.oneoffice.jp
  • include: webcas.net
  • ip: 13.115.170.248
  • ip: 18.179.209.252
  • ip: 202.232.241.181
  • ip: 202.232.241.182
  • ip: 202.32.71.53
  • ip: 202.32.71.54
  • ip: 202.32.71.57

Threat-feed evidence

History

Related pages

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