Skip to content

Hostname

veza.by

Last fetched

veza.by resolves to 51.250.120.229, announced in 51.250.120.0/22 by YandexCloud - Yandex.Cloud LLC in RU. veza.by 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 · veza.byRouting diversity1.5/10Peering density5.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/veza.by

Resolution chain

IPv6 resolution

No AAAA record for veza.by is recorded in WhisperGraph.

Attribution

Yandex

esp · ORIGIN_AS

WHOIS identity

Registrar
registrar:reliable software, ltd

Subdomains

Subdomain
bx24.veza.by
www.veza.by

Showing 2 of 3. 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

Sample outbound links

Mail and authentication

Nameservers

  • u1.hoster.by
  • u2.hoster.by

MX records

  • mailbe02.hoster.by

SPF policy

  • include: _spf.hoster.by
  • a: veza.by
  • mx: veza.by

Threat-feed evidence

History

Related pages

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