Skip to content

Hostname

botsman.org

Last fetched

botsman.org resolves to 185.246.64.136, announced in 185.246.64.0/23 by RU-JSCIOT - JSC IOT in RU. botsman.org 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 · botsman.orgRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/botsman.org

Resolution chain

Attribution

jsc iot

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
ermachenok aleksei andreevich
Contact emails
php-masters@yandex.ru

Subdomains

Subdomain
www.botsman.org

Showing 1 of 1 subdomain (1 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

  • ns1.r01.ru
  • ns2.r01.ru

MX records

  • mx.yandex.net

SPF policy

  • include: _spf.yandex.net
  • ip: 185.246.64.136

Threat-feed evidence

History

Related pages

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