Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: The Netherlands

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 145.175.8.69
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54051
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;145.175.8.69.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Dec 20 06:27:31 CST 2025
;; MSG SIZE  rcvd: 105
Host info
69.8.175.145.in-addr.arpa domain name pointer 145.175.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
69.8.175.145.in-addr.arpa	name = 145.175.EARLY-REGISTRATION.of.SURFnet.invalid.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
23.88.167.194 attackspam
Unauthorized connection attempt from IP address 23.88.167.194 on Port 445(SMB)
2020-04-26 23:58:42
159.203.108.196 attackbots
SSH Brute Force
2020-04-27 00:17:40
112.84.210.92 attackbotsspam
failed_logins
2020-04-27 00:22:02
49.235.69.80 attack
Apr 26 07:50:15 server1 sshd\[19332\]: Invalid user sethi from 49.235.69.80
Apr 26 07:50:15 server1 sshd\[19332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.69.80 
Apr 26 07:50:16 server1 sshd\[19332\]: Failed password for invalid user sethi from 49.235.69.80 port 48038 ssh2
Apr 26 07:55:25 server1 sshd\[20808\]: Invalid user wdg from 49.235.69.80
Apr 26 07:55:25 server1 sshd\[20808\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.69.80 
...
2020-04-26 23:39:16
5.135.101.228 attackbots
Apr 26 02:44:55 php1 sshd\[14489\]: Invalid user mariadb from 5.135.101.228
Apr 26 02:44:55 php1 sshd\[14489\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.135.101.228
Apr 26 02:44:57 php1 sshd\[14489\]: Failed password for invalid user mariadb from 5.135.101.228 port 46372 ssh2
Apr 26 02:48:49 php1 sshd\[14797\]: Invalid user at from 5.135.101.228
Apr 26 02:48:49 php1 sshd\[14797\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.135.101.228
2020-04-26 23:53:41
142.93.174.47 attackbotsspam
Apr 26 16:57:35 legacy sshd[32484]: Failed password for root from 142.93.174.47 port 32846 ssh2
Apr 26 17:01:45 legacy sshd[32566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.174.47
Apr 26 17:01:47 legacy sshd[32566]: Failed password for invalid user linjk from 142.93.174.47 port 46696 ssh2
...
2020-04-27 00:18:37
54.38.139.210 attackbots
detected by Fail2Ban
2020-04-27 00:04:42
117.4.242.101 attack
Unauthorized connection attempt from IP address 117.4.242.101 on Port 445(SMB)
2020-04-26 23:52:05
148.251.66.48 attackbotsspam
xmlrpc attack
2020-04-26 23:33:27
51.158.152.7 attack
Lines containing failures of 51.158.152.7
Apr 26 13:54:49 shared05 sshd[25895]: Invalid user test from 51.158.152.7 port 36830
Apr 26 13:54:50 shared05 sshd[25895]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.158.152.7
Apr 26 13:54:52 shared05 sshd[25895]: Failed password for invalid user test from 51.158.152.7 port 36830 ssh2
Apr 26 13:54:52 shared05 sshd[25895]: Received disconnect from 51.158.152.7 port 36830:11: Bye Bye [preauth]
Apr 26 13:54:52 shared05 sshd[25895]: Disconnected from invalid user test 51.158.152.7 port 36830 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=51.158.152.7
2020-04-26 23:38:10
201.219.209.220 attack
Unauthorized connection attempt from IP address 201.219.209.220 on Port 445(SMB)
2020-04-26 23:47:01
14.175.89.163 attack
Unauthorized connection attempt from IP address 14.175.89.163 on Port 445(SMB)
2020-04-26 23:55:27
52.41.197.179 attack
Lines containing failures of 52.41.197.179
Apr 26 12:56:35 expertgeeks postfix/smtpd[24338]: connect from em3-52-41-197-179.us-west-2.compute.amazonaws.com[52.41.197.179]
Apr 26 12:56:35 expertgeeks policyd-spf[24343]: Softfail; identhostnamey=helo; client-ip=52.41.197.179; helo=shape.com; envelope-from=x@x
Apr x@x
Apr 26 12:56:36 expertgeeks policyd-spf[24343]: Softfail; identhostnamey=helo; client-ip=52.41.197.179; helo=shape.com; envelope-from=x@x
Apr x@x
Apr 26 12:56:39 expertgeeks policyd-spf[24343]: Softfail; identhostnamey=helo; client-ip=52.41.197.179; helo=shape.com; envelope-from=x@x
Apr x@x
Apr 26 12:56:43 expertgeeks policyd-spf[24343]: Softfail; identhostnamey=helo; client-ip=52.41.197.179; helo=shape.com; envelope-from=x@x
Apr x@x
Apr 26 12:56:48 expertgeeks policyd-spf[24343]: Softfail; identhostnamey=helo; client-ip=52.41.197.179; helo=shape.com; envelope-from=x@x
Apr x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=52.41.197.179
2020-04-26 23:53:16
141.136.90.142 attack
Unauthorized connection attempt from IP address 141.136.90.142 on Port 445(SMB)
2020-04-27 00:22:57
200.60.60.84 attackspambots
Repeated brute force against a port
2020-04-27 00:17:16

Recently Reported IPs

213.47.208.251 135.191.220.102 180.30.8.61 72.153.105.187
139.38.69.120 209.149.28.93 66.35.52.148 100.19.113.251
254.116.236.244 185.249.143.118 222.169.235.123 1.130.113.145
86.124.15.96 170.161.57.30 9.165.35.224 136.226.61.183
110.167.171.66 207.158.159.206 227.29.31.85 70.249.113.123