Skip to content

Hostname

beam.to

Last fetched

beam.to resolves to 52.60.87.163, announced in 52.60.64.0/18 by AMAZON-02 - Amazon.com, Inc. in CA. beam.to is listed by 2 threat feeds; reconciled level MEDIUM.

Threat posture

24threat score (procedure-native scale)

MEDIUM

Listed by 2 threat feeds. Advisory: popularity-trust-offset.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:21 GMT
Last seen on a feed
Mon, 14 Sep 2026 19:54:13 GMT

Nutrition Label

WHISPER CANON · beam.toRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/beam.to

Resolution chain

IPv6 resolution

No AAAA record for beam.to is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for beam.to. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
www.beam.to

Showing 1 of 1 subdomain (1 per page).

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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.101domain.com
  • ns2.101domain.com
  • ns5.101domain.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

Threat-feed evidence

History

Related pages

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