Skip to content

Hostname

application.batel.by

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

jsc iot

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for application.batel.by. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
www.application.batel.by

Showing 1 of 1 subdomain (1 per page).

Threat-feed evidence

History

Related pages

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