必须是合法有效的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所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 124.120.45.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54429
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;124.120.45.45.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 10:18:44 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
45.45.120.124.in-addr.arpa domain name pointer ppp-124-120-45-45.revip2.asianet.co.th.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.45.120.124.in-addr.arpa	name = ppp-124-120-45-45.revip2.asianet.co.th.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
217.170.205.107 attack
CMS (WordPress or Joomla) login attempt.
2020-03-24 06:01:32
165.227.96.190 attackbotsspam
Mar 23 17:08:07 Tower sshd[29390]: Connection from 165.227.96.190 port 37046 on 192.168.10.220 port 22 rdomain ""
Mar 23 17:08:07 Tower sshd[29390]: Invalid user vn from 165.227.96.190 port 37046
Mar 23 17:08:07 Tower sshd[29390]: error: Could not get shadow information for NOUSER
Mar 23 17:08:07 Tower sshd[29390]: Failed password for invalid user vn from 165.227.96.190 port 37046 ssh2
Mar 23 17:08:07 Tower sshd[29390]: Received disconnect from 165.227.96.190 port 37046:11: Bye Bye [preauth]
Mar 23 17:08:07 Tower sshd[29390]: Disconnected from invalid user vn 165.227.96.190 port 37046 [preauth]
2020-03-24 05:31:48
103.78.81.227 attackbots
2020-03-23T18:27:13.916430jannga.de sshd[20152]: Invalid user ha from 103.78.81.227 port 47576
2020-03-23T18:27:16.091230jannga.de sshd[20152]: Failed password for invalid user ha from 103.78.81.227 port 47576 ssh2
...
2020-03-24 05:44:40
167.114.131.19 attackspam
Tried sshing with brute force.
2020-03-24 06:02:48
68.65.123.228 attack
Attempt to hack Wordpress Login, XMLRPC or other login
2020-03-24 06:03:54
117.84.93.253 attackbots
IP reached maximum auth failures
2020-03-24 05:38:44
200.233.3.31 attack
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2020-03-24 06:02:22
31.13.115.10 attackspam
[Mon Mar 23 22:43:11.118040 2020] [:error] [pid 25293:tid 140519810295552] [client 31.13.115.10:42894] [client 31.13.115.10] ModSecurity: Access denied with code 403 (phase 2). Match of "eq 0" against "&REQUEST_HEADERS:Transfer-Encoding" required. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "202"] [id "920171"] [msg "GET or HEAD Request with Transfer-Encoding."] [data "1"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/INVALID_HREQ"] [tag "CAPEC-272"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/particle-v20.js"] [unique_id "XnjZD7dSec56q6n39A6CEAAAAAE"]
...
2020-03-24 05:30:17
128.201.137.252 attackbots
Fail2Ban - FTP Abuse Attempt
2020-03-24 05:49:34
124.205.224.179 attack
$f2bV_matches
2020-03-24 05:58:56
200.60.60.84 attack
(sshd) Failed SSH login from 200.60.60.84 (PE/Peru/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 23 18:23:55 s1 sshd[4205]: Invalid user woodward from 200.60.60.84 port 35125
Mar 23 18:23:58 s1 sshd[4205]: Failed password for invalid user woodward from 200.60.60.84 port 35125 ssh2
Mar 23 18:35:40 s1 sshd[4429]: Invalid user vidhyanath from 200.60.60.84 port 35426
Mar 23 18:35:42 s1 sshd[4429]: Failed password for invalid user vidhyanath from 200.60.60.84 port 35426 ssh2
Mar 23 18:45:02 s1 sshd[4577]: Invalid user setup from 200.60.60.84 port 43809
2020-03-24 05:44:21
49.89.249.3 attackbots
Mar 23 16:21:12 garuda postfix/smtpd[38227]: connect from unknown[49.89.249.3]
Mar 23 16:21:14 garuda postfix/smtpd[38227]: warning: unknown[49.89.249.3]: SASL LOGIN authentication failed: generic failure
Mar 23 16:21:14 garuda postfix/smtpd[38227]: lost connection after AUTH from unknown[49.89.249.3]
Mar 23 16:21:14 garuda postfix/smtpd[38227]: disconnect from unknown[49.89.249.3] ehlo=1 auth=0/1 commands=1/2
Mar 23 16:21:42 garuda postfix/smtpd[38227]: connect from unknown[49.89.249.3]
Mar 23 16:21:43 garuda postfix/smtpd[38227]: warning: unknown[49.89.249.3]: SASL LOGIN authentication failed: generic failure
Mar 23 16:21:43 garuda postfix/smtpd[38227]: lost connection after AUTH from unknown[49.89.249.3]
Mar 23 16:21:43 garuda postfix/smtpd[38227]: disconnect from unknown[49.89.249.3] ehlo=1 auth=0/1 commands=1/2
Mar 23 16:22:29 garuda postfix/smtpd[38227]: connect from unknown[49.89.249.3]
Mar 23 16:22:35 garuda postfix/smtpd[38227]: warning: unknown[49.89.249.3]: S........
-------------------------------
2020-03-24 05:42:16
111.231.255.52 attack
Mar 23 21:12:23 serwer sshd\[2061\]: Invalid user jori from 111.231.255.52 port 41634
Mar 23 21:12:23 serwer sshd\[2061\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.255.52
Mar 23 21:12:25 serwer sshd\[2061\]: Failed password for invalid user jori from 111.231.255.52 port 41634 ssh2
...
2020-03-24 05:35:09
58.87.75.178 attack
Mar 23 22:01:32 jane sshd[31273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.87.75.178 
Mar 23 22:01:34 jane sshd[31273]: Failed password for invalid user ux from 58.87.75.178 port 38498 ssh2
...
2020-03-24 05:52:53
151.67.18.149 attack
Mi manda attacchi DDoS senza motivo
2020-03-24 05:54:14

最近上报的IP列表

124.120.45.42 124.120.45.47 124.120.45.59 124.120.45.6
124.120.45.60 124.120.45.78 124.120.45.84 124.120.45.94
124.120.45.98 14.130.196.213 124.120.46.106 124.120.46.115
124.120.46.12 124.120.46.121 124.120.46.123 124.120.46.124
124.120.46.129 124.120.75.124 124.120.75.130 124.120.75.144