Skip to content

Hostname

baycrews.jp

Last fetched

baycrews.jp resolves to 4 IPv4 addresses operated by AKAMAI-AS - Akamai Technologies, Inc. in IN.

Nutrition Label

WHISPER CANON · baycrews.jpRouting diversity3.5/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency3.3/10Resolver footprint8.6/10canon.whisper.security/host/baycrews.jp

Resolution chain

baycrews.jp resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
104.120.70.148104.120.64.0/19AS16625AKAMAI-AS - Akamai Technologies, Inc.IN
23.0.183.21723.0.176.0/20AS16625AKAMAI-AS - Akamai Technologies, Inc.ID
23.63.121.10523.63.112.0/20AS16625AKAMAI-AS - Akamai Technologies, Inc.DE
23.67.133.5523.67.128.0/20AS16625AKAMAI-AS - Akamai Technologies, Inc.DE

WHOIS identity

Registrar
—
Organization
—
Contact emails

Subdomains

24 observed subdomains of baycrews.jp.

Subdomain
app-api.baycrews.jp
backend-api.baycrews.jp
backoffice.baycrews.jp
cts.baycrews.jp
dev.baycrews.jp
em465.baycrews.jp
gocuxy.baycrews.jp
images.baycrews.jp
internal.baycrews.jp
mpfs.baycrews.jp
production.baycrews.jp
sgtm.baycrews.jp
staging.baycrews.jp
stg-images.baycrews.jp
wait.baycrews.jp
www.baycrews.jp

Showing 16 of 24. View all subdomains →

Web-graph footprint

Distinct hostnames that link to or from baycrews.jp in the public web crawl.

1,677 sites link to this hostname.

126 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

11 SPF mechanisms authorising senders for baycrews.jp.

MechanismTarget
SPF_INCLUDE_spf.salesforce.com
SPF_INCLUDEamazonses.com
SPF_INCLUDEem465.baycrews.jp
SPF_INCLUDEspf.protection.outlook.com
SPF_INCLUDEwebcas.net
SPF_IP115.30.0.171/32
SPF_IP115.30.0.172/32
SPF_IP124.109.181.7/32
SPF_IP54.238.179.102
SPF_IP54.238.205.235
SPF_IP54.238.206.244

Related pages

Pivot deeper into the graph from baycrews.jp.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "baycrews.jp"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.