Skip to content

Hostname

bluesphere.jp

Last fetched

bluesphere.jp resolves to 108.156.39.115, announced in 108.156.32.0/21 by AMAZON-02 - Amazon.com, Inc. in GB. bluesphere.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 · bluesphere.jpRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/bluesphere.jp

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
(not displayed by registrant's request)
Contact emails
proxy@whoisprotectservice.com

Subdomains

Subdomain
box.bluesphere.jp
chk-001.bluesphere.jp
dev-partner.bluesphere.jp
fmapi.bluesphere.jp
partner.bluesphere.jp
portal.bluesphere.jp
promoter.bluesphere.jp
ptnfmapi.bluesphere.jp
report.bluesphere.jp
waf0001.bluesphere.jp
waf0003.bluesphere.jp
waf0005.bluesphere.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

Mail and authentication

Nameservers

  • ns-440.awsdns-55.com
  • ns-964.awsdns-56.net
  • ns-1311.awsdns-35.org
  • ns-1652.awsdns-14.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: spf.am.arara.com
  • include: _spf.google.com
  • include: _spf.activegate-ss.jp
  • ip: 183.182.45.254
  • ip: 183.182.49.20
  • ip: 203.141.155.242

Threat-feed evidence

History

Related pages

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