Skip to content

Hostname

ecom-plus.ru

Last fetched

ecom-plus.ru resolves to 212.164.140.129, announced in 212.164.136.0/21 by ROSTELECOM-AS - PJSC Rostelecom in RU. ecom-plus.ru 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 · ecom-plus.ruRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.0/10canon.whisper.security/host/ecom-plus.ru

Resolution chain

IPv6 resolution

No AAAA record for ecom-plus.ru is recorded in WhisperGraph.

Attribution

pjsc rostelecom

ORIGIN_AS

WHOIS identity

Registrar
registrar:ru-center-ru
Registrant organisation
jsc russian post

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

  • d01ns1.russianpost.ru
  • d02ns1.russianpost.ru
  • r00ns2.russianpost.ru

MX records

  • r00smtpmm.ecom-plus.ru
  • r00exedge03.main.russianpost.ru
  • r00exedge01.main.russianpost.ru
  • d01smtpmm.ecom-plus.ru
  • d02exedge02.main.russianpost.ru
  • r00smtpmm.russianpost.ru
  • r00exedge02.main.russianpost.ru
  • d02exedge03.main.russianpost.ru
  • d02exedge01.main.russianpost.ru
  • d01smtpmm.russianpost.ru
  • r00ksmg02.main.russianpost.ru
  • d02ksmg02.main.russianpost.ru
  • d02ksmg03.main.russianpost.ru
  • r00ksmg01.main.russianpost.ru
  • r00ksmg03.main.russianpost.ru
  • d01ksmg01.main.russianpost.ru
  • d02ksmg01.main.russianpost.ru

Threat-feed evidence

History

Related pages

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