Skip to content

Hostname

podbor.ru

Last fetched

podbor.ru resolves to 185.134.204.236, announced in 185.134.204.0/24 by ROSBUSINESSCONSULTING-AS - ROSBUSINESSCONSULTING JSC in RU. podbor.ru is listed by 1 threat feed; reconciled level HIGH.

Threat posture

50threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:51:25 GMT
Last seen on a feed
Sat, 12 Sep 2026 19:45:18 GMT

Nutrition Label

WHISPER CANON · podbor.ruRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/podbor.ru

Resolution chain

IPv6 resolution

No AAAA record for podbor.ru is recorded in WhisperGraph.

Attribution

rosbusinessconsulting jsc

ORIGIN_AS

WHOIS identity

Registrar
registrar:ru-center-ru
Registrant organisation
'loveplanet'

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns.loveplanet.ru
  • ns2.loveplanet.ru

MX records

  • mx2.rbc.ru
  • mx3.rbc.ru
  • smtp.rbc.ru

Threat-feed evidence

History

Related pages

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