Skip to content

Hostname

besto24.com

Last fetched

besto24.com resolves to 83.149.95.205, announced in 83.149.64.0/18 by LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. in NL. besto24.com 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 · besto24.comRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/besto24.com

Resolution chain

IPv6 resolution

No AAAA record for besto24.com is recorded in WhisperGraph.

Attribution

leaseweb netherlands

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:106
Registrant organisation
kristine tomsone-pruse
Contact emails
tomsonepruse@gmail.com

Subdomains

Subdomain
besto2.besto24.com
cpanel.besto24.com
cpcalendars.besto24.com
cpcontacts.besto24.com
mail.besto24.com
webdisk.besto24.com
webmail.besto24.com
www.besto24.com

Showing 8 of 9. 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

  • ns1.areait.lv
  • ns2.areait.lv
  • ns3.areait.lv
  • 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

MX records

  • besto24.com

SPF policy

  • ip: 95.211.48.179/32
  • ip: 95.168.166.47/32
  • a: besto24.com
  • mx: besto24.com
  • include: relay.mailchannels.net
  • ip: 212.32.225.85
  • ip: 212.32.225.92
  • ip: 212.7.207.88
  • ip: 83.149.95.205

Threat-feed evidence

History

Related pages

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