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

城市(city): unknown

省份(region): unknown

国家(country): Kyrgyzstan

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 109.201.190.190
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59737
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;109.201.190.190.		IN	A

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

;; Query time: 92 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 17:57:21 CST 2022
;; MSG SIZE  rcvd: 108
HOST信息:
190.190.201.109.in-addr.arpa domain name pointer 109-201-190-190.mega.kg.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
190.190.201.109.in-addr.arpa	name = 109-201-190-190.mega.kg.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
114.67.72.164 attack
Apr  7 17:30:04 icinga sshd[11654]: Failed password for root from 114.67.72.164 port 43394 ssh2
Apr  7 17:34:13 icinga sshd[18723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.72.164 
Apr  7 17:34:15 icinga sshd[18723]: Failed password for invalid user user from 114.67.72.164 port 55070 ssh2
...
2020-04-08 02:56:17
1.179.185.50 attackbotsspam
Dec 16 02:07:21 mail sshd\[9945\]: Invalid user share from 1.179.185.50 port 38206
Dec 16 02:07:21 mail sshd\[9945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.185.50
Dec 16 02:07:23 mail sshd\[9945\]: Failed password for invalid user share from 1.179.185.50 port 38206 ssh2
Dec 16 02:13:54 mail sshd\[14167\]: Invalid user test from 1.179.185.50 port 49058
Dec 16 02:13:54 mail sshd\[14167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.185.50
...
2020-04-08 02:51:47
89.247.39.219 attackspambots
Apr  7 12:46:14 www_kotimaassa_fi sshd[25073]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.247.39.219
Apr  7 12:46:16 www_kotimaassa_fi sshd[25073]: Failed password for invalid user user from 89.247.39.219 port 43682 ssh2
...
2020-04-08 03:21:12
37.142.138.52 attackbotsspam
Apr  7 18:42:49 ncomp sshd[9515]: Invalid user admin from 37.142.138.52
Apr  7 18:42:49 ncomp sshd[9515]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.142.138.52
Apr  7 18:42:49 ncomp sshd[9515]: Invalid user admin from 37.142.138.52
Apr  7 18:42:50 ncomp sshd[9515]: Failed password for invalid user admin from 37.142.138.52 port 54725 ssh2
2020-04-08 02:57:16
104.248.114.67 attack
(sshd) Failed SSH login from 104.248.114.67 (US/United States/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Apr  7 14:15:46 host sshd[60447]: Invalid user irc from 104.248.114.67 port 58174
2020-04-08 03:05:17
101.95.131.122 attack
Unauthorized connection attempt from IP address 101.95.131.122 on Port 445(SMB)
2020-04-08 03:14:20
190.204.233.140 attackbots
Unauthorized connection attempt from IP address 190.204.233.140 on Port 445(SMB)
2020-04-08 03:13:20
82.64.15.106 attackspambots
Apr  7 16:24:08 marvibiene sshd[16318]: Invalid user pi from 82.64.15.106 port 42814
Apr  7 16:24:08 marvibiene sshd[16320]: Invalid user pi from 82.64.15.106 port 42818
...
2020-04-08 02:54:14
64.94.208.254 attackspambots
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across hesschiropracticsc.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://ww
2020-04-08 03:00:44
118.27.9.229 attackspambots
Apr  7 17:13:55 localhost sshd\[30951\]: Invalid user ubuntu from 118.27.9.229 port 48838
Apr  7 17:13:55 localhost sshd\[30951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.27.9.229
Apr  7 17:13:58 localhost sshd\[30951\]: Failed password for invalid user ubuntu from 118.27.9.229 port 48838 ssh2
...
2020-04-08 03:25:26
171.239.179.203 attack
Unauthorized connection attempt from IP address 171.239.179.203 on Port 445(SMB)
2020-04-08 03:15:57
23.104.184.243 attackspam
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - positivelychiropractic.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across positivelychiropractic.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally
2020-04-08 03:05:41
46.39.20.4 attackbotsspam
Apr  7 16:13:38 vps647732 sshd[17488]: Failed password for root from 46.39.20.4 port 40464 ssh2
...
2020-04-08 03:24:05
103.95.48.210 attack
Unauthorized connection attempt from IP address 103.95.48.210 on Port 445(SMB)
2020-04-08 03:16:54
111.229.116.240 attackspam
Apr  7 19:03:30 h1745522 sshd[21341]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.116.240  user=root
Apr  7 19:03:32 h1745522 sshd[21341]: Failed password for root from 111.229.116.240 port 52256 ssh2
Apr  7 19:07:28 h1745522 sshd[21582]: Invalid user deploy from 111.229.116.240 port 39044
Apr  7 19:07:28 h1745522 sshd[21582]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.116.240
Apr  7 19:07:28 h1745522 sshd[21582]: Invalid user deploy from 111.229.116.240 port 39044
Apr  7 19:07:30 h1745522 sshd[21582]: Failed password for invalid user deploy from 111.229.116.240 port 39044 ssh2
Apr  7 19:11:27 h1745522 sshd[21929]: Invalid user zimbra from 111.229.116.240 port 54064
Apr  7 19:11:27 h1745522 sshd[21929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.116.240
Apr  7 19:11:27 h1745522 sshd[21929]: Invalid user zimbra from 111.229.116.240
...
2020-04-08 03:08:40

最近上报的IP列表

109.201.191.89 109.201.191.239 109.201.2.90 109.201.20.154
109.201.197.131 109.201.193.176 109.201.20.236 109.201.20.195
109.201.19.194 109.201.20.200 109.201.193.161 109.201.20.249
109.201.20.226 109.201.20.50 109.201.20.120 109.201.200.228
109.201.198.182 109.201.20.7 109.201.204.123 109.201.205.140