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

城市(city): Kowloon City

省份(region): Kowloon City Kowloon

国家(country): Hong Kong

运营商(isp): CSL Limited

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;118.140.132.10.			IN	A

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

;; Query time: 44 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Dec 05 14:05:47 CST 2024
;; MSG SIZE  rcvd: 107
HOST信息:
Host 10.132.140.118.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 10.132.140.118.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
37.152.177.25 attackspambots
Jun 27 07:00:11 zulu412 sshd\[24034\]: Invalid user ubuntu from 37.152.177.25 port 60622
Jun 27 07:00:11 zulu412 sshd\[24034\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.152.177.25
Jun 27 07:00:14 zulu412 sshd\[24034\]: Failed password for invalid user ubuntu from 37.152.177.25 port 60622 ssh2
...
2020-06-27 19:04:32
35.222.194.118 attackbots
2020-06-26T16:34:30.850186hostname sshd[21927]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.194.222.35.bc.googleusercontent.com  user=root
2020-06-26T16:34:32.618475hostname sshd[21927]: Failed password for root from 35.222.194.118 port 48152 ssh2
2020-06-26T16:37:59.903343hostname sshd[24809]: Invalid user user9 from 35.222.194.118 port 48450
...
2020-06-27 19:43:24
104.131.46.166 attackbotsspam
Jun 27 08:38:10 web8 sshd\[23257\]: Invalid user mc2 from 104.131.46.166
Jun 27 08:38:10 web8 sshd\[23257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.46.166
Jun 27 08:38:12 web8 sshd\[23257\]: Failed password for invalid user mc2 from 104.131.46.166 port 57404 ssh2
Jun 27 08:42:22 web8 sshd\[25343\]: Invalid user nsc from 104.131.46.166
Jun 27 08:42:22 web8 sshd\[25343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.46.166
2020-06-27 19:26:00
193.174.89.19 attack
\[Sat Jun 27 07:22:55 2020\] \[error\] \[client 193.174.89.19\] Invalid URI in request GET stager64 HTTP/1.1
\[Sat Jun 27 07:22:55 2020\] \[error\] \[client 193.174.89.19\] Invalid URI in request GET stager HTTP/1.1
...
2020-06-27 19:33:37
35.194.70.48 attack
2020-06-27T09:46:05+0000 Failed SSH Authentication/Brute Force Attack. (Server 6)
2020-06-27 19:43:40
51.178.78.153 attackspam
Jun 27 12:54:28 mail postfix/submission/smtpd[17352]: lost connection after UNKNOWN from ns3167284.ip-51-178-78.eu[51.178.78.153]
...
2020-06-27 19:10:57
198.46.222.55 attackbots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found loischiropractic.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 th
2020-06-27 19:22:40
132.232.248.82 attackbots
Jun 27 11:33:02 h1745522 sshd[28804]: Invalid user bao from 132.232.248.82 port 46014
Jun 27 11:33:02 h1745522 sshd[28804]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.248.82
Jun 27 11:33:02 h1745522 sshd[28804]: Invalid user bao from 132.232.248.82 port 46014
Jun 27 11:33:05 h1745522 sshd[28804]: Failed password for invalid user bao from 132.232.248.82 port 46014 ssh2
Jun 27 11:35:22 h1745522 sshd[28940]: Invalid user peru from 132.232.248.82 port 41652
Jun 27 11:35:22 h1745522 sshd[28940]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.248.82
Jun 27 11:35:22 h1745522 sshd[28940]: Invalid user peru from 132.232.248.82 port 41652
Jun 27 11:35:24 h1745522 sshd[28940]: Failed password for invalid user peru from 132.232.248.82 port 41652 ssh2
Jun 27 11:37:41 h1745522 sshd[29057]: Invalid user user from 132.232.248.82 port 37280
...
2020-06-27 19:06:30
20.185.32.70 attack
Invalid user admin from 20.185.32.70 port 6622
2020-06-27 19:37:00
27.50.169.167 attackspam
Jun 27 05:45:06 game-panel sshd[21641]: Failed password for root from 27.50.169.167 port 56216 ssh2
Jun 27 05:47:59 game-panel sshd[21798]: Failed password for root from 27.50.169.167 port 58690 ssh2
Jun 27 05:50:54 game-panel sshd[21936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.50.169.167
2020-06-27 19:23:51
103.216.48.245 attackspam
103.216.48.245 - - [27/Jun/2020:11:31:38 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
103.216.48.245 - - [27/Jun/2020:11:31:39 +0100] "POST /wp-login.php HTTP/1.1" 200 5429 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
103.216.48.245 - - [27/Jun/2020:11:51:09 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
...
2020-06-27 19:03:36
94.23.172.28 attackspam
SSH bruteforce
2020-06-27 19:03:21
45.78.43.205 attackbotsspam
Jun 27 13:08:31 nas sshd[10721]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.78.43.205 
Jun 27 13:08:33 nas sshd[10721]: Failed password for invalid user marcelo from 45.78.43.205 port 40082 ssh2
Jun 27 13:12:24 nas sshd[10917]: Failed password for root from 45.78.43.205 port 44964 ssh2
...
2020-06-27 19:40:12
52.237.220.70 attack
Jun 27 12:36:19 srv-ubuntu-dev3 sshd[124054]: Invalid user azureadmin from 52.237.220.70
Jun 27 12:36:19 srv-ubuntu-dev3 sshd[124054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.237.220.70
Jun 27 12:36:19 srv-ubuntu-dev3 sshd[124054]: Invalid user azureadmin from 52.237.220.70
Jun 27 12:36:21 srv-ubuntu-dev3 sshd[124054]: Failed password for invalid user azureadmin from 52.237.220.70 port 20531 ssh2
Jun 27 12:42:23 srv-ubuntu-dev3 sshd[125136]: Invalid user azureadmin from 52.237.220.70
Jun 27 12:42:23 srv-ubuntu-dev3 sshd[125136]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.237.220.70
Jun 27 12:42:23 srv-ubuntu-dev3 sshd[125136]: Invalid user azureadmin from 52.237.220.70
Jun 27 12:42:24 srv-ubuntu-dev3 sshd[125136]: Failed password for invalid user azureadmin from 52.237.220.70 port 60662 ssh2
Jun 27 12:42:57 srv-ubuntu-dev3 sshd[125241]: Invalid user azureadmin from 52.237.220.70
...
2020-06-27 19:33:20
103.45.150.111 attackbotsspam
Invalid user test from 103.45.150.111 port 41242
2020-06-27 19:02:32

最近上报的IP列表

93.123.85.18 183.222.62.226 136.251.84.91 247.63.23.74
10.8.51.146 112.74.80.195 104.218.140.249 157.78.29.99
154.90.44.239 249.243.185.6 172.194.33.170 2.248.45.118
118.121.41.19 208.243.183.23 43.60.70.48 163.152.128.113
76.223.44.107 146.53.79.206 253.75.223.18 93.17.152.98