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

城市(city): unknown

省份(region): unknown

国家(country): None

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
IP 类型 评论内容 时间
114.104.135.56 attackbotsspam
Oct  2 01:01:11 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:22 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:38 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:57 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:02:09 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-03 04:06:13
114.104.135.56 attackbots
Oct  2 01:01:11 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:22 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:38 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:57 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:02:09 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-03 02:53:05
114.104.135.56 attackbots
Oct  2 01:01:11 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:22 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:38 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:57 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:02:09 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-02 23:24:58
114.104.135.56 attack
Oct  2 01:01:11 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:22 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:38 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:57 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:02:09 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-02 19:57:05
114.104.135.56 attackspam
Oct  2 01:01:11 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:22 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:38 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:57 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:02:09 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-02 16:29:56
114.104.135.56 attack
Oct  2 01:01:11 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:22 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:38 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:01:57 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  2 01:02:09 srv01 postfix/smtpd\[27252\]: warning: unknown\[114.104.135.56\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-02 12:48:15
114.104.135.224 attack
Sep 30 22:55:35 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:55:46 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:56:02 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:56:20 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:56:32 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-02 01:59:08
114.104.135.224 attackbots
Sep 30 22:55:35 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:55:46 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:56:02 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:56:20 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 30 22:56:32 srv01 postfix/smtpd\[12021\]: warning: unknown\[114.104.135.224\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-10-01 18:06:20
114.104.135.60 attackbotsspam
Sep 23 22:45:22 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:48:53 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:04 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:20 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:38 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-09-25 00:24:53
114.104.135.60 attack
Sep 23 22:45:22 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:48:53 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:04 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:20 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:38 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-09-24 16:05:15
114.104.135.60 attack
Sep 23 22:45:22 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:48:53 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:04 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:20 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 23 22:49:38 srv01 postfix/smtpd\[24920\]: warning: unknown\[114.104.135.60\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-09-24 07:29:59
114.104.135.144 attackbots
Aug 22 07:44:15 srv01 postfix/smtpd\[5710\]: warning: unknown\[114.104.135.144\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 22 07:44:26 srv01 postfix/smtpd\[5710\]: warning: unknown\[114.104.135.144\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 22 07:44:44 srv01 postfix/smtpd\[5710\]: warning: unknown\[114.104.135.144\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 22 07:45:04 srv01 postfix/smtpd\[5710\]: warning: unknown\[114.104.135.144\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 22 07:45:15 srv01 postfix/smtpd\[5710\]: warning: unknown\[114.104.135.144\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-08-22 16:09:39
114.104.135.51 attackspam
Aug 15 07:36:50 srv01 postfix/smtpd\[21398\]: warning: unknown\[114.104.135.51\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 07:37:02 srv01 postfix/smtpd\[21398\]: warning: unknown\[114.104.135.51\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 07:37:18 srv01 postfix/smtpd\[21398\]: warning: unknown\[114.104.135.51\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 07:37:38 srv01 postfix/smtpd\[21398\]: warning: unknown\[114.104.135.51\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 07:37:49 srv01 postfix/smtpd\[21398\]: warning: unknown\[114.104.135.51\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-08-15 16:23:28
114.104.135.59 attackbots
Aug  5 08:48:19 srv01 postfix/smtpd\[14222\]: warning: unknown\[114.104.135.59\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug  5 08:48:31 srv01 postfix/smtpd\[14222\]: warning: unknown\[114.104.135.59\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug  5 08:48:48 srv01 postfix/smtpd\[14222\]: warning: unknown\[114.104.135.59\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug  5 08:49:07 srv01 postfix/smtpd\[14222\]: warning: unknown\[114.104.135.59\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug  5 08:49:19 srv01 postfix/smtpd\[14222\]: warning: unknown\[114.104.135.59\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-08-05 20:13:35
114.104.135.127 attackspambots
Jul  3 22:57:36 srv01 postfix/smtpd\[17412\]: warning: unknown\[114.104.135.127\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  3 22:57:47 srv01 postfix/smtpd\[17412\]: warning: unknown\[114.104.135.127\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  3 22:58:03 srv01 postfix/smtpd\[17412\]: warning: unknown\[114.104.135.127\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  3 22:58:21 srv01 postfix/smtpd\[17412\]: warning: unknown\[114.104.135.127\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jul  3 22:58:32 srv01 postfix/smtpd\[17412\]: warning: unknown\[114.104.135.127\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-07-04 06:58:52
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.104.135.202
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44710
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.104.135.202.		IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 14:33:46 CST 2022
;; MSG SIZE  rcvd: 108
HOST信息:
Host 202.135.104.114.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 202.135.104.114.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
58.218.66.7 attackspam
Portscan or hack attempt detected by psad/fwsnort
2019-06-21 21:09:33
103.120.224.10 attackspambots
20 attempts against mh-ssh on wave.magehost.pro
2019-06-21 20:47:42
116.206.15.24 attackbotsspam
Portscanning on different or same port(s).
2019-06-21 20:42:13
178.128.119.134 attackspambots
Jun 19 14:21:37 pi01 sshd[29930]: Connection from 178.128.119.134 port 54806 on 192.168.1.10 port 22
Jun 19 14:21:39 pi01 sshd[29930]: Invalid user discord from 178.128.119.134 port 54806
Jun 19 14:21:39 pi01 sshd[29930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.119.134
Jun 19 14:21:41 pi01 sshd[29930]: Failed password for invalid user discord from 178.128.119.134 port 54806 ssh2
Jun 19 14:21:41 pi01 sshd[29930]: Received disconnect from 178.128.119.134 port 54806:11: Bye Bye [preauth]
Jun 19 14:21:41 pi01 sshd[29930]: Disconnected from 178.128.119.134 port 54806 [preauth]
Jun 19 14:25:58 pi01 sshd[30027]: Connection from 178.128.119.134 port 41658 on 192.168.1.10 port 22
Jun 19 14:25:59 pi01 sshd[30027]: Invalid user kong from 178.128.119.134 port 41658
Jun 19 14:25:59 pi01 sshd[30027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.119.134
Jun 19 14:26:01 pi01 sshd[........
-------------------------------
2019-06-21 21:09:58
159.65.175.37 attackspam
Invalid user chimistry from 159.65.175.37 port 18346
2019-06-21 20:40:23
218.98.32.150 attack
phpmyadmin
2019-06-21 20:29:08
198.108.67.59 attack
8991/tcp 1000/tcp 5672/tcp...
[2019-04-20/06-21]119pkt,115pt.(tcp)
2019-06-21 20:45:04
222.112.250.9 attack
Jun 21 11:17:09 ns37 sshd[7131]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.112.250.9
2019-06-21 20:22:29
134.175.181.138 attack
Jun 21 10:01:38 MK-Soft-VM7 sshd\[19420\]: Invalid user cloud from 134.175.181.138 port 52916
Jun 21 10:01:38 MK-Soft-VM7 sshd\[19420\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.181.138
Jun 21 10:01:39 MK-Soft-VM7 sshd\[19420\]: Failed password for invalid user cloud from 134.175.181.138 port 52916 ssh2
...
2019-06-21 21:08:33
1.100.115.153 attackbots
2019-06-21T11:53:14.994715scmdmz1 sshd\[27647\]: Invalid user mysqldump from 1.100.115.153 port 56168
2019-06-21T11:53:14.998266scmdmz1 sshd\[27647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.100.115.153
2019-06-21T11:53:16.662646scmdmz1 sshd\[27647\]: Failed password for invalid user mysqldump from 1.100.115.153 port 56168 ssh2
...
2019-06-21 20:50:34
201.81.14.177 attackbotsspam
Jun 21 13:46:03 dedicated sshd[16488]: Invalid user django from 201.81.14.177 port 57248
Jun 21 13:46:05 dedicated sshd[16488]: Failed password for invalid user django from 201.81.14.177 port 57248 ssh2
Jun 21 13:46:03 dedicated sshd[16488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.81.14.177
Jun 21 13:46:03 dedicated sshd[16488]: Invalid user django from 201.81.14.177 port 57248
Jun 21 13:46:05 dedicated sshd[16488]: Failed password for invalid user django from 201.81.14.177 port 57248 ssh2
2019-06-21 21:11:57
142.44.202.51 attackspam
142.44.202.51 - - [21/Jun/2019:11:14:16 +0200] "GET /wp-includes/css/modules.php HTTP/1.1" 404 16363 "-" "python-requests/2.18.4"
142.44.202.51 - - [21/Jun/2019:11:14:20 +0200] "GET /wso.php HTTP/1.1" 404 16525 "-" "python-requests/2.18.4"
142.44.202.51 - - [21/Jun/2019:11:14:24 +0200] "GET /wp-content/plugins/upspy/ HTTP/1.1" 404 11538 "-" "python-requests/2.18.4"
142.44.202.51 - - [21/Jun/2019:11:14:28 +0200] "GET /wp-content/plugins/ubh/ HTTP/1.1" 404 11682 "-" "python-requests/2.18.4"
142.44.202.51 - - [21/Jun/2019:11:14:34 +0200] "GET /wp-content/plugins/vwcleanerplugin/bump.php?cache HTTP/1.1" 404 16592 "-" "python-requests/2.18.4"
...
2019-06-21 21:14:06
61.219.11.153 attackbots
Portscanning on different or same port(s).
2019-06-21 20:51:58
62.173.149.176 attack
Jun 21 11:16:51 [munged] sshd[31378]: Invalid user         2019-06-21 20:29:44
123.16.140.255 attackspam
445/tcp
[2019-06-21]1pkt
2019-06-21 21:10:29

最近上报的IP列表

114.104.135.210 114.104.135.20 114.104.135.214 114.104.135.217
114.104.135.221 113.250.157.3 114.104.135.226 114.104.135.230
114.104.135.212 114.104.135.233 114.104.135.23 114.104.135.235
114.104.135.238 114.104.135.237 114.104.135.229 114.104.135.240
114.104.135.24 113.250.157.38 114.104.135.222 114.104.135.243