Skip to content

Hostname

batel.by

Last fetched

batel.by resolves to 212.109.222.119, announced in 212.109.222.0/24 by RU-JSCIOT - JSC IOT in RU. batel.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 · batel.byRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint4.6/10canon.whisper.security/host/batel.by

Resolution chain

IPv6 resolution

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

Attribution

jsc iot

ORIGIN_AS

WHOIS identity

Registrar
registrar:open contact, ltd
Registrant organisation
ooo <<??????>>

Subdomains

Subdomain
2.batel.by
2019.batel.by
2020.batel.by
a.batel.by
adm.batel.by
admin.batel.by
api.batel.by
app.batel.by
application.batel.by
backup.batel.by
beta.batel.by
bi.batel.by

Showing 12 of 292. View all subdomains →

Mail and authentication

Nameservers

  • dns1.yandex.net
  • dns2.yandex.net
  • dns1.yandex.ru
  • dns2.yandex.ru

MX records

  • mx.yandex.net

SPF policy

  • redirect: _spf.yandex.net

Threat-feed evidence

History

Related pages

Pivot from batel.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: "batel.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.