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

城市(city): unknown

省份(region): unknown

国家(country): Netherlands

运营商(isp): 3NT Solutions LLP

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): Data Center/Web Hosting/Transit

用户上报:
类型 评论内容 时间
attackspambots
"Unrouteable address"
2020-03-28 08:32:57
相同子网IP讨论:
IP 类型 评论内容 时间
5.45.68.133 attackbotsspam
ET CINS Active Threat Intelligence Poor Reputation IP group 5 - port: 55611 proto: tcp cat: Misc Attackbytes: 60
2020-10-01 07:26:06
5.45.68.133 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 5 - port: 55608 proto: tcp cat: Misc Attackbytes: 60
2020-09-30 23:53:40
5.45.68.133 attackspambots
(PERMBLOCK) 5.45.68.133 (NL/Netherlands/-) has had more than 4 temp blocks in the last 86400 secs; Ports: *; Direction: inout; Trigger: LF_PERMBLOCK_COUNT; Logs:
2020-09-30 16:19:14
5.45.68.189 attackbotsspam
Dear Sir / Madam, 
Yesterday, my close friend (Simona Simova) was contacted via fake Facebook profile to be informed that she has a profile on a escort website. While researching via the German phone number used in the advert, we have came across more ads. These profiles are created without her permission and she is now very upset. 

Here is a list of the profiles we have found: 

- https://escortsofia.info/de/sia-11/ (5.45.68.189)
- https://escortsofia.info/de/eleonora-8/ (5.45.68.189)
- https://escortinberlin.info/eleonora-3/ (5.45.68.189)
- https://escortinberlin.info/sia-2/ (5.45.68.189)

We have already hired a lawyer in Germany who will escalate the issue to the authorities.
2020-04-24 03:31:08
5.45.68.19 attackspam
WP Authentication failure
2019-07-15 18:24:20
5.45.68.19 attackspam
SQL Injection Exploit Attempts
2019-07-01 05:07:03
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 5.45.68.15
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16852
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;5.45.68.15.			IN	A

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

;; Query time: 100 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 28 08:32:54 CST 2020
;; MSG SIZE  rcvd: 114
HOST信息:
15.68.45.5.in-addr.arpa domain name pointer darkhost.pro.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
15.68.45.5.in-addr.arpa	name = darkhost.pro.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
180.101.125.76 attackspam
Dec 17 18:49:20 MK-Soft-Root2 sshd[26329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.125.76 
Dec 17 18:49:22 MK-Soft-Root2 sshd[26329]: Failed password for invalid user wsh from 180.101.125.76 port 56468 ssh2
...
2019-12-18 04:05:34
89.122.82.47 attackbotsspam
Dec 17 15:20:49 debian-2gb-nbg1-2 kernel: \[245227.735010\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.122.82.47 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=41775 PROTO=TCP SPT=23065 DPT=23 WINDOW=32313 RES=0x00 SYN URGP=0
2019-12-18 04:34:32
221.226.58.102 attackspam
Dec 17 11:05:43 server sshd\[26183\]: Failed password for invalid user terry from 221.226.58.102 port 35834 ssh2
Dec 17 17:12:34 server sshd\[32316\]: Invalid user aywie from 221.226.58.102
Dec 17 17:12:34 server sshd\[32316\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.226.58.102 
Dec 17 17:12:36 server sshd\[32316\]: Failed password for invalid user aywie from 221.226.58.102 port 46206 ssh2
Dec 17 17:20:46 server sshd\[2328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.226.58.102  user=vcsa
...
2019-12-18 04:37:06
45.82.153.83 attackspam
Dec 17 21:23:53 srv01 postfix/smtpd\[30540\]: warning: unknown\[45.82.153.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 17 21:24:13 srv01 postfix/smtpd\[5794\]: warning: unknown\[45.82.153.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 17 21:24:14 srv01 postfix/smtpd\[30540\]: warning: unknown\[45.82.153.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 17 21:24:33 srv01 postfix/smtpd\[5794\]: warning: unknown\[45.82.153.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 17 21:29:31 srv01 postfix/smtpd\[30540\]: warning: unknown\[45.82.153.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-18 04:35:32
190.114.247.10 attackbots
RDPBrutePLe24
2019-12-18 04:37:26
121.241.7.34 attackspambots
Port 1433 Scan
2019-12-18 04:09:20
111.93.7.2 attack
1576592463 - 12/17/2019 15:21:03 Host: 111.93.7.2/111.93.7.2 Port: 445 TCP Blocked
2019-12-18 04:19:16
201.161.58.37 attackspambots
Dec 17 21:15:28 itv-usvr-01 sshd[25795]: Invalid user willey from 201.161.58.37
Dec 17 21:15:28 itv-usvr-01 sshd[25795]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.161.58.37
Dec 17 21:15:28 itv-usvr-01 sshd[25795]: Invalid user willey from 201.161.58.37
Dec 17 21:15:30 itv-usvr-01 sshd[25795]: Failed password for invalid user willey from 201.161.58.37 port 40111 ssh2
Dec 17 21:21:20 itv-usvr-01 sshd[26053]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.161.58.37  user=lp
Dec 17 21:21:22 itv-usvr-01 sshd[26053]: Failed password for lp from 201.161.58.37 port 45763 ssh2
2019-12-18 04:01:04
202.137.20.58 attackspam
SSH brute-force: detected 36 distinct usernames within a 24-hour window.
2019-12-18 04:04:14
211.227.23.193 attackbotsspam
Dec 17 06:51:26 php1 sshd\[12560\]: Invalid user farlie from 211.227.23.193
Dec 17 06:51:26 php1 sshd\[12560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.227.23.193
Dec 17 06:51:28 php1 sshd\[12560\]: Failed password for invalid user farlie from 211.227.23.193 port 25131 ssh2
Dec 17 06:57:58 php1 sshd\[13520\]: Invalid user tsekiguc from 211.227.23.193
Dec 17 06:57:58 php1 sshd\[13520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.227.23.193
2019-12-18 03:59:49
196.218.130.66 attackbots
firewall-block, port(s): 23/tcp
2019-12-18 04:32:29
131.100.158.53 attack
...
2019-12-18 04:06:21
103.129.223.149 attackspam
Unauthorized SSH login attempts
2019-12-18 04:19:33
178.62.23.60 attackbotsspam
Lines containing failures of 178.62.23.60 (max 1000)
Dec 16 16:06:33 localhost sshd[1675]: Invalid user tomcat from 178.62.23.60 port 45288
Dec 16 16:06:33 localhost sshd[1675]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.23.60 
Dec 16 16:06:34 localhost sshd[1675]: Failed password for invalid user tomcat from 178.62.23.60 port 45288 ssh2
Dec 16 16:06:35 localhost sshd[1675]: Received disconnect from 178.62.23.60 port 45288:11: Bye Bye [preauth]
Dec 16 16:06:35 localhost sshd[1675]: Disconnected from invalid user tomcat 178.62.23.60 port 45288 [preauth]
Dec 16 16:12:53 localhost sshd[3065]: Invalid user vanusa from 178.62.23.60 port 37758
Dec 16 16:12:53 localhost sshd[3065]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.23.60 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=178.62.23.60
2019-12-18 04:18:57
66.249.64.192 attackspambots
Automatic report - Banned IP Access
2019-12-18 04:12:00

最近上报的IP列表

178.184.64.180 159.233.113.58 185.86.210.78 196.193.0.16
18.122.147.130 104.88.112.82 245.146.140.238 236.244.232.232
123.20.127.34 149.166.62.44 124.20.133.119 153.39.165.232
188.214.39.61 107.221.159.123 119.65.16.221 239.102.192.185
147.243.232.252 90.181.161.1 171.239.212.106 76.95.131.242