Skip to content

Hostname

bea.rs

Last fetched

bea.rs resolves to 23.108.56.123, announced in 23.108.32.0/19 by LEASEWEB-USA-MIA - Leaseweb USA, Inc. in US. bea.rs 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 · bea.rsRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.9/10canon.whisper.security/host/bea.rs

Resolution chain

IPv6 resolution

No AAAA record for bea.rs is recorded in WhisperGraph.

Attribution

leaseweb usa

ORIGIN_AS

WHOIS identity

Registrar
iana:1204

Subdomains

Subdomain
1.bea.rs
email.bea.rs
email2.bea.rs
en-us.bea.rs
es-ar.bea.rs
it-it.bea.rs
ns.bea.rs
ns1.bea.rs
ns2.bea.rs
pt-br.bea.rs
s1.bea.rs
s2.bea.rs

Showing 12 of 18. 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

  • ns2.nossowebsite.net.br
  • ns.nws.net.br
  • ns1.nws.net.br
  • ns2.nws.net.br
  • 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.bea.rs
  • ns1.bea.rs
  • ns2.bea.rs
  • ns1.nossowebsite.net,br

MX records

  • nws.net.br
  • stargate.nossowebsite.net.br

SPF policy

  • include: sendgrid.net
  • include: u1944076.wl.sendgrid.net
  • a: bea.rs
  • mx: bea.rs
  • ip: 107.182.233.172
  • ip: 98.158.176.20

Threat-feed evidence

History

Related pages

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