必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): Atyrau

省份(region): Atyrau

国家(country): Kazakhstan

运营商(isp): Kazakhtelecom

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '89.218.166.156 - 89.218.166.159'

% Abuse contact for '89.218.166.156 - 89.218.166.159' is 'abuse@telecom.kz'

inetnum:        89.218.166.156 - 89.218.166.159
netname:        POLIKLINIKA
descr:          POLIKLINIKA
country:        KZ
admin-c:        ZK1451-RIPE
tech-c:         ZK1451-RIPE
status:         ASSIGNED PA
mnt-by:         KNIC-MNT
created:        2018-02-12T05:51:20Z
last-modified:  2018-02-12T05:51:20Z
source:         RIPE

person:         Zhumagalieva Kauralai
address:        Atyrau. Aiteke bi  str 24
address:        KZ
phone:          +7 7122 271899
nic-hdl:        ZK1451-RIPE
mnt-by:         KNIC-MNT
created:        2018-02-12T05:51:20Z
last-modified:  2018-02-12T05:51:20Z
source:         RIPE

% Information related to '89.218.166.0/24AS9198'

route:          89.218.166.0/24
descr:          Kazakhtelecom Megaline Atyrau Network
origin:         AS9198
mnt-by:         KNIC-MNT
created:        2008-05-14T08:21:46Z
last-modified:  2008-05-14T08:21:46Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.122.1 (DEXTER)
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 89.218.166.158
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55769
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;89.218.166.158.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026060802 1800 900 604800 86400

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jun 09 13:00:38 CST 2026
;; MSG SIZE  rcvd: 107
HOST信息:
158.166.218.89.in-addr.arpa domain name pointer 89.218.166.158.metro.online.kz.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
158.166.218.89.in-addr.arpa	name = 89.218.166.158.metro.online.kz.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
107.175.158.44 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found palmerchiroga.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software that
2020-08-11 03:50:51
177.67.222.244 attackbots
Automatic report - Banned IP Access
2020-08-11 04:09:54
182.254.166.215 attack
Banned for a week because repeated abuses, for example SSH, but not only
2020-08-11 03:42:45
141.98.10.195 attackspam
2020-08-10T19:37:43.296189abusebot-5.cloudsearch.cf sshd[16040]: Invalid user 1234 from 141.98.10.195 port 59770
2020-08-10T19:37:43.301612abusebot-5.cloudsearch.cf sshd[16040]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.195
2020-08-10T19:37:43.296189abusebot-5.cloudsearch.cf sshd[16040]: Invalid user 1234 from 141.98.10.195 port 59770
2020-08-10T19:37:44.852116abusebot-5.cloudsearch.cf sshd[16040]: Failed password for invalid user 1234 from 141.98.10.195 port 59770 ssh2
2020-08-10T19:38:18.296055abusebot-5.cloudsearch.cf sshd[16164]: Invalid user user from 141.98.10.195 port 46906
2020-08-10T19:38:18.302027abusebot-5.cloudsearch.cf sshd[16164]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.195
2020-08-10T19:38:18.296055abusebot-5.cloudsearch.cf sshd[16164]: Invalid user user from 141.98.10.195 port 46906
2020-08-10T19:38:19.656851abusebot-5.cloudsearch.cf sshd[16164]: Failed pass
...
2020-08-11 03:42:22
103.84.37.146 attack
Unauthorized connection attempt from IP address 103.84.37.146 on Port 445(SMB)
2020-08-11 04:10:11
192.99.210.162 attack
SSH brute-force attempt
2020-08-11 04:05:03
123.207.153.52 attackbotsspam
Banned for a week because repeated abuses, for example SSH, but not only
2020-08-11 03:53:00
115.159.53.215 attackbotsspam
Aug 10 03:19:45 vm0 sshd[6626]: Failed password for root from 115.159.53.215 port 39608 ssh2
Aug 10 15:34:06 vm0 sshd[8300]: Failed password for root from 115.159.53.215 port 7599 ssh2
...
2020-08-11 03:55:09
107.175.240.151 attackspambots
 TCP (SYN) 107.175.240.151:59198 -> port 23, len 44
2020-08-11 03:40:08
35.230.162.59 attackspam
10.08.2020 17:12:03 - Wordpress fail 
Detected by ELinOX-ALM
2020-08-11 04:10:57
190.207.115.5 attackspam
Unauthorized connection attempt from IP address 190.207.115.5 on Port 445(SMB)
2020-08-11 04:03:33
202.155.228.207 attack
Aug 10 20:07:13 * sshd[6768]: Failed password for root from 202.155.228.207 port 52892 ssh2
2020-08-11 04:00:46
49.236.203.163 attackbots
Aug 10 08:49:15 ws24vmsma01 sshd[244649]: Failed password for root from 49.236.203.163 port 59036 ssh2
Aug 10 09:00:55 ws24vmsma01 sshd[1855]: Failed password for root from 49.236.203.163 port 58326 ssh2
...
2020-08-11 03:51:19
152.32.229.70 attackspambots
Banned for a week because repeated abuses, for example SSH, but not only
2020-08-11 04:16:11
106.13.28.108 attack
Aug 10 21:20:01 h2779839 sshd[11112]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.28.108  user=root
Aug 10 21:20:03 h2779839 sshd[11112]: Failed password for root from 106.13.28.108 port 49868 ssh2
Aug 10 21:22:04 h2779839 sshd[11143]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.28.108  user=root
Aug 10 21:22:07 h2779839 sshd[11143]: Failed password for root from 106.13.28.108 port 51582 ssh2
Aug 10 21:24:10 h2779839 sshd[11157]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.28.108  user=root
Aug 10 21:24:12 h2779839 sshd[11157]: Failed password for root from 106.13.28.108 port 53296 ssh2
Aug 10 21:26:16 h2779839 sshd[11175]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.28.108  user=root
Aug 10 21:26:18 h2779839 sshd[11175]: Failed password for root from 106.13.28.108 port 55014 ssh2
Aug 
...
2020-08-11 03:58:16

最近上报的IP列表

182.16.91.194 58.65.142.142 116.212.142.238 34.78.23.28
183.36.35.195 2606:4700:10::6816:4167 2606:4700:10::6816:2389 2606:4700:10::6816:1599
10.34.56.18 10.22.38.218 34.156.179.1 64.62.156.150
37.148.135.220 35.205.116.15 180.153.236.143 69.5.169.52
69.5.169.32 2606:4700:10::6814:6921 81.28.13.14 72.1.180.63