Skip to content

Hostname

bay.security

Last fetched

bay.security resolves to 35.219.200.248, announced in 35.216.0.0/14 by GOOGLE-2 - Google LLC in US. bay.security 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 · bay.securityRouting diversity1.5/10Peering density5.3/10MOAS conflict⚠ 2 conflictsThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/bay.security

Resolution chain

IPv6 resolution

No AAAA record for bay.security is recorded in WhisperGraph.

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146

Subdomains

Subdomain
_spfm.bay.security
app.bay.security
dev.bay.security
micron.bay.security
platform.bay.security
prod.bay.security
status.bay.security
test-platform.bay.security
www.bay.security

Showing 9 of 16. View all subdomains →

Mail and authentication

Nameservers

  • ns-261.awsdns-32.com
  • ns41.domaincontrol.com
  • ns42.domaincontrol.com
  • ns-907.awsdns-49.net
  • 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
  • ns-1366.awsdns-42.org
  • ns-1981.awsdns-55.co.uk

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: dc-aa8e722993._spfm.bay.security

Threat-feed evidence

History

Related pages

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