Skip to content

Hostname

azoom.jp

Last fetched

azoom.jp resolves to 35.244.171.130, announced in 35.244.0.0/16 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. azoom.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 · azoom.jpRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/azoom.jp

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
space lab,
Contact emails
whoisproxy@value-domain.com

Subdomains

Subdomain
aapa-api.azoom.jp
aapa.azoom.jp
auth-pg.azoom.jp
azgram.azoom.jp
birman-api.azoom.jp
carparking-admin-mb.azoom.jp
column-management.azoom.jp
corporate.azoom.jp
customer.azoom.jp
doc-gallery-api.azoom.jp
fax-api.azoom.jp
fax.azoom.jp

Showing 12 of 73. 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-cloud-e1.googledomains.com
  • ns-cloud-e2.googledomains.com
  • ns-cloud-e3.googledomains.com
  • ns-cloud-e4.googledomains.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: _spf.activegate-ss.jp
  • mx: azoom.jp
  • include: _prspf.guardianwall.jp

Threat-feed evidence

History

Related pages

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