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

城市(city): unknown

省份(region): unknown

国家(country): Germany

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;149.216.5.134.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 15:28:23 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 134.5.216.149.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.5.216.149.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
177.1.214.207 attack
Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-10-01T17:05:22Z and 2020-10-01T17:13:02Z
2020-10-02 05:03:50
125.165.107.120 attack
WordPress login attack
2020-10-02 04:59:20
94.26.117.190 attack
SSH login attempts with user root.
2020-10-02 04:45:37
35.202.157.96 attack
35.202.157.96 - - [01/Oct/2020:13:55:22 +0100] "POST /wp-login.php HTTP/1.1" 200 2348 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
35.202.157.96 - - [01/Oct/2020:13:55:23 +0100] "POST /wp-login.php HTTP/1.1" 200 2328 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
35.202.157.96 - - [01/Oct/2020:13:55:24 +0100] "POST /wp-login.php HTTP/1.1" 200 2376 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-10-02 04:53:00
114.101.247.45 attackspam
Sep 30 20:41:09 marvibiene sshd[19214]: Invalid user admin1 from 114.101.247.45 port 58318
Sep 30 20:41:09 marvibiene sshd[19214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.101.247.45
Sep 30 20:41:09 marvibiene sshd[19214]: Invalid user admin1 from 114.101.247.45 port 58318
Sep 30 20:41:11 marvibiene sshd[19214]: Failed password for invalid user admin1 from 114.101.247.45 port 58318 ssh2
2020-10-02 04:47:30
190.244.125.190 attackspambots
Sep 30 22:33:29 server770 sshd[17896]: Did not receive identification string from 190.244.125.190 port 55657
Sep 30 22:33:55 server770 sshd[17901]: Invalid user user from 190.244.125.190 port 55974
Sep 30 22:33:56 server770 sshd[17901]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.244.125.190
Sep 30 22:33:57 server770 sshd[17901]: Failed password for invalid user user from 190.244.125.190 port 55974 ssh2
Sep 30 22:33:58 server770 sshd[17901]: Connection closed by 190.244.125.190 port 55974 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=190.244.125.190
2020-10-02 05:06:50
129.152.141.71 attackbots
Oct  1 11:22:15 localhost sshd\[30944\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.152.141.71  user=root
Oct  1 11:22:17 localhost sshd\[30944\]: Failed password for root from 129.152.141.71 port 13564 ssh2
Oct  1 11:35:38 localhost sshd\[31172\]: Invalid user recepcao from 129.152.141.71 port 37207
...
2020-10-02 04:58:58
185.228.133.4 attackspam
(sshd) Failed SSH login from 185.228.133.4 (RU/Russia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  1 11:37:25 optimus sshd[2926]: Invalid user ntps from 185.228.133.4
Oct  1 11:37:25 optimus sshd[2926]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.228.133.4 
Oct  1 11:37:27 optimus sshd[2926]: Failed password for invalid user ntps from 185.228.133.4 port 50641 ssh2
Oct  1 11:45:21 optimus sshd[5469]: Invalid user ly from 185.228.133.4
Oct  1 11:45:21 optimus sshd[5469]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.228.133.4
2020-10-02 05:11:23
157.230.59.44 attackbots
$f2bV_matches
2020-10-02 05:10:06
85.209.0.101 attackspam
Oct  1 23:35:23 server2 sshd\[18425\]: User root from 85.209.0.101 not allowed because not listed in AllowUsers
Oct  1 23:35:24 server2 sshd\[18423\]: User root from 85.209.0.101 not allowed because not listed in AllowUsers
Oct  1 23:35:24 server2 sshd\[18426\]: User root from 85.209.0.101 not allowed because not listed in AllowUsers
Oct  1 23:35:24 server2 sshd\[18428\]: User root from 85.209.0.101 not allowed because not listed in AllowUsers
Oct  1 23:35:24 server2 sshd\[18424\]: User root from 85.209.0.101 not allowed because not listed in AllowUsers
Oct  1 23:35:24 server2 sshd\[18422\]: User root from 85.209.0.101 not allowed because not listed in AllowUsers
2020-10-02 04:48:14
185.74.4.189 attackspam
Invalid user test2007 from 185.74.4.189 port 45226
2020-10-02 05:11:35
103.208.137.2 attack
Oct  1 21:21:23  sshd\[19549\]: User root from 103.208.137.2 not allowed because not listed in AllowUsersOct  1 21:21:24  sshd\[19549\]: Failed password for invalid user root from 103.208.137.2 port 43454 ssh2
...
2020-10-02 05:01:28
46.101.151.97 attack
Oct  1 21:45:27 fhem-rasp sshd[32210]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.151.97
Oct  1 21:45:29 fhem-rasp sshd[32210]: Failed password for invalid user job from 46.101.151.97 port 44398 ssh2
...
2020-10-02 04:51:49
145.239.110.129 attackspam
2020-10-01 20:53:57,039 fail2ban.actions: WARNING [ssh] Ban 145.239.110.129
2020-10-02 05:19:21
51.195.63.170 attackbots
Fail2Ban Ban Triggered
2020-10-02 04:49:05

最近上报的IP列表

147.23.116.105 184.34.128.86 97.205.36.53 241.78.220.201
38.147.61.168 171.5.197.199 56.163.163.46 155.141.2.153
174.47.19.235 74.60.75.16 41.97.188.50 87.228.229.145
41.178.92.202 160.114.66.220 228.162.189.212 190.60.144.73
208.166.81.78 65.28.151.17 145.102.99.64 79.219.139.213