Skip to content

Hostname

randka.be

Last fetched

randka.be resolves to 57.128.240.11, announced in 57.128.192.0/18 by OVH - OVH SAS in PL. randka.be 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 · randka.beRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/randka.be

Resolution chain

IPv6 resolution

No AAAA record for randka.be is recorded in WhisperGraph.

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:ovh

Subdomains

Subdomain
mail.randka.be
webmail.randka.be
www.randka.be

Showing 3 of 3 subdomains (3 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

  • dns105.ovh.net
  • ns105.ovh.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

MX records

  • randka.be
  • mx.serwer1.plmail.ovh
  • mx.maildate.pl
  • mx.miledate.pl
  • mx.senddate.pl

SPF policy

  • a: randka.be
  • mx: randka.be
  • include: spf.serwer1.plmail.ovh
  • include: spf.maildate.pl
  • include: spf.miledate.pl
  • include: spf.senddate.pl
  • ip: 194.164.26.226
  • ip: 212.227.144.152
  • ip: 51.75.44.102
  • ip: 51.77.44.29
  • ip: 51.77.44.62
  • ip: 51.77.46.180
  • ip: 51.77.47.183
  • ip: 51.83.166.186
  • ip: 51.83.167.76
  • ip: 57.128.240.11
  • ip: 87.106.122.190

Threat-feed evidence

History

Related pages

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