Skip to content

Hostname

wirebag.jp

Last fetched

wirebag.jp resolves to 52.196.177.255, announced in 52.196.0.0/14 by AMAZON-02 - Amazon.com, Inc. in JP. wirebag.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 · wirebag.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.0/10canon.whisper.security/host/wirebag.jp

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

Registrant organisation
yuichi ozaki
Contact emails
office_ec@anteprima.co.jp, office_it_icd@anteprima.co.jp, ozaki_yuichi@anteprima.co.jp

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

  • ns6-tk01.ocn.ad.jp
  • ns6-tk02.ocn.ad.jp
  • 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

  • recvml.wirebag.jp

SPF policy

  • ip: 154.33.63.0/24
  • ip: 182.48.8.32/27
  • include: amazonses.com
  • include: mdroof.maildealer.jp
  • include: spf.wirebag.jp
  • include: anteprima-spf.scinable.net
  • ip: 133.223.28.151
  • ip: 133.223.65.52

Threat-feed evidence

History

Related pages

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