158.160.180.2
An address in Moscow, Russia, announced by Yandex.Cloud LLC (AS200350). Of our anonymity, network and service databases, it is in Hosting IP, SSH IP, and Web IP.
9 of 24 address-keyed databases hold it
Summary
- HostingYandex Cloud
No mobile carrier, anycast or CDN
- SSHPort 22
- WebPort 443
Geolocation
Where the address is, and what that place uses.
- City
- Moscow
- Region
- Moscow
- Postal code
- 101000
- Country
- Russia
- Continent
- Europe
- Coordinates
- 55.7520, 37.6178
- Timezone
- Europe/Moscow
Ownership
Who holds the address: the AS announcing it, the registry record, the abuse contact and its name in DNS.
- Company
- Yandex.Cloud LLC
- Domain
- yandex-team.ru
- Type
- Hosting
- Registered in
- Russia
- AS number
- AS200350
- Name
- Yandex.Cloud LLC
- Prefix
- 158.160.0.0/16
- RPKI
- Valid
- Type
- Hosting
- Registered in
- Russia
- Name
- Yandex.Cloud LLC
- Handle
- RU-YANDEXCLOUD
- Organization
- ORG-YL62-RIPE
- Status
- LEGACY
- Registry
- RIPE NCC
- Domain
- yandex-team.ru
- Name
- Abuse-C Role
- Address
- 16 Lva Tolstovo str, 119021, Moscow, RUSSIAN FEDERATION
- Network
- 158.160.0.0-158.160.255.255
Anonymity
Whether the address hides someone else: a VPN, Tor, a relay, a proxy pool, or a hosting range.
Network
What kind of network it is on: a mobile carrier, an anycast service, a CDN edge.
Services
What our own internet-wide measurement found listening on it.
- Port
- 22
- Banner
- SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.14
- Host key
- SHA256:68397e38da1395e43e2357a4ffb4d39d16b6d16269c7693c85b260eabfa4632f
- Handshake
- Completed
- First seen
- 2026-07-19
- Last seen
- 2026-10-04
- 443 status
- 301
- 443 redirect
- http://www.google.com/
- 443 server
- gws
- 443 title
- 301 Moved
- 443 TLS
- TLSv1.3
- 443 certificate
- invalid2.invalid
- 443 issuer
- OU=No SNI provided - please fix your client., CN=invalid2.invalid
- 443 browser-trusted
- No
- 443 seen
- 2026-07-25 to 2026-10-02
Test the real build first.
An evaluation license puts a full current build in your hands, with no sampling, so you can measure it against your own traffic before anyone talks about terms.