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: Utrecht

Region: Utrecht

Country: 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:
IP Type Details Datetime
89.248.172.16 attack
Bap IP
2024-05-12 23:39:04
89.248.172.140 attackbots
Automatic report - Port Scan
2020-10-13 20:36:52
89.248.172.140 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 80 - port: 2468 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 12:08:47
89.248.172.140 attackspambots
ET DROP Dshield Block Listed Source group 1 - port: 7110 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 04:58:27
89.248.172.16 attack
ET DROP Dshield Block Listed Source group 1 - port: 60001 proto: tcp cat: Misc Attackbytes: 60
2020-10-11 03:06:34
89.248.172.16 attackspambots
[N3.H3.VM3] Port Scanner Detected Blocked by UFW
2020-10-10 18:56:46
89.248.172.16 attackbotsspam
- Port=2081
2020-10-08 03:13:38
89.248.172.16 attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 78 - port: 8089 proto: tcp cat: Misc Attackbytes: 60
2020-10-07 19:27:51
89.248.172.85 attackbots
scans 5 times in preceeding hours on the ports (in chronological order) 28589 10777 30026 10201 30103 resulting in total of 70 scans from 89.248.160.0-89.248.174.255 block.
2020-10-01 07:13:00
89.248.172.140 attack
scans 10 times in preceeding hours on the ports (in chronological order) 2728 4590 4446 3410 20222 1983 5656 6300 2728 3031 resulting in total of 70 scans from 89.248.160.0-89.248.174.255 block.
2020-10-01 06:47:26
89.248.172.85 attack
 TCP (SYN) 89.248.172.85:50104 -> port 30009, len 44
2020-09-30 23:39:40
89.248.172.140 attackspam
 TCP (SYN) 89.248.172.140:44912 -> port 3410, len 44
2020-09-30 23:10:43
89.248.172.140 attack
firewall-block, port(s): 1983/tcp, 3450/tcp, 5656/tcp
2020-09-30 15:44:03
89.248.172.140 attackbots
 TCP (SYN) 89.248.172.140:47677 -> port 2000, len 44
2020-09-21 20:38:47
89.248.172.140 attackbots
ET DROP Dshield Block Listed Source group 1 - port: 5566 proto: tcp cat: Misc Attackbytes: 60
2020-09-21 12:30:09
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 89.248.172.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35159
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;89.248.172.74.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 16 10:37:05 CST 2022
;; MSG SIZE  rcvd: 106
Host info
74.172.248.89.in-addr.arpa domain name pointer no-reverse-dns-configured.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
74.172.248.89.in-addr.arpa	name = no-reverse-dns-configured.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
89.135.122.109 attack
Dec  4 05:46:09 firewall sshd[22869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.135.122.109
Dec  4 05:46:09 firewall sshd[22869]: Invalid user rpc from 89.135.122.109
Dec  4 05:46:11 firewall sshd[22869]: Failed password for invalid user rpc from 89.135.122.109 port 43400 ssh2
...
2019-12-04 17:53:40
5.39.82.197 attack
Dec  4 11:40:09 sauna sshd[30104]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.82.197
Dec  4 11:40:11 sauna sshd[30104]: Failed password for invalid user pros from 5.39.82.197 port 48616 ssh2
...
2019-12-04 18:11:44
51.75.170.116 attack
Dec  4 12:36:19 server sshd\[18859\]: Invalid user Arho from 51.75.170.116
Dec  4 12:36:19 server sshd\[18859\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.ip-51-75-170.eu 
Dec  4 12:36:21 server sshd\[18859\]: Failed password for invalid user Arho from 51.75.170.116 port 54950 ssh2
Dec  4 12:43:40 server sshd\[20779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.ip-51-75-170.eu  user=root
Dec  4 12:43:42 server sshd\[20779\]: Failed password for root from 51.75.170.116 port 39958 ssh2
...
2019-12-04 17:51:30
111.198.54.177 attack
Fail2Ban - SSH Bruteforce Attempt
2019-12-04 18:23:23
106.52.6.248 attackbots
Dec  4 10:22:47 OPSO sshd\[25115\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.6.248  user=root
Dec  4 10:22:50 OPSO sshd\[25115\]: Failed password for root from 106.52.6.248 port 54202 ssh2
Dec  4 10:29:58 OPSO sshd\[26901\]: Invalid user jana from 106.52.6.248 port 34188
Dec  4 10:29:58 OPSO sshd\[26901\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.6.248
Dec  4 10:30:00 OPSO sshd\[26901\]: Failed password for invalid user jana from 106.52.6.248 port 34188 ssh2
2019-12-04 18:10:56
162.247.74.200 attackspam
12/04/2019-09:10:38.925149 162.247.74.200 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 14
2019-12-04 18:25:51
45.35.14.209 attackspambots
Host Scan
2019-12-04 18:05:37
51.254.204.190 attack
Dec  4 12:23:31 server sshd\[15119\]: Invalid user schibig from 51.254.204.190
Dec  4 12:23:31 server sshd\[15119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.ip-51-254-204.eu 
Dec  4 12:23:33 server sshd\[15119\]: Failed password for invalid user schibig from 51.254.204.190 port 60104 ssh2
Dec  4 12:28:47 server sshd\[16545\]: Invalid user usuario from 51.254.204.190
Dec  4 12:28:47 server sshd\[16545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.ip-51-254-204.eu 
...
2019-12-04 18:09:04
118.25.14.19 attackbots
Dec  4 10:37:13 ArkNodeAT sshd\[15187\]: Invalid user ricedore from 118.25.14.19
Dec  4 10:37:13 ArkNodeAT sshd\[15187\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.14.19
Dec  4 10:37:15 ArkNodeAT sshd\[15187\]: Failed password for invalid user ricedore from 118.25.14.19 port 47880 ssh2
2019-12-04 17:46:31
112.64.170.178 attack
Nov 28 20:34:00 microserver sshd[12919]: Invalid user dieter from 112.64.170.178 port 27811
Nov 28 20:34:00 microserver sshd[12919]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.170.178
Nov 28 20:34:02 microserver sshd[12919]: Failed password for invalid user dieter from 112.64.170.178 port 27811 ssh2
Nov 28 20:38:26 microserver sshd[13595]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.170.178  user=root
Nov 28 20:38:28 microserver sshd[13595]: Failed password for root from 112.64.170.178 port 22538 ssh2
Nov 28 20:50:38 microserver sshd[15469]: Invalid user password12345 from 112.64.170.178 port 5508
Nov 28 20:50:38 microserver sshd[15469]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.170.178
Nov 28 20:50:40 microserver sshd[15469]: Failed password for invalid user password12345 from 112.64.170.178 port 5508 ssh2
Nov 28 20:52:50 microserver sshd[15596]: Invalid
2019-12-04 17:49:20
217.182.95.16 attackspambots
Dec  4 12:25:43 hosting sshd[27252]: Invalid user dbps from 217.182.95.16 port 50186
Dec  4 12:25:43 hosting sshd[27252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.95.16
Dec  4 12:25:43 hosting sshd[27252]: Invalid user dbps from 217.182.95.16 port 50186
Dec  4 12:25:45 hosting sshd[27252]: Failed password for invalid user dbps from 217.182.95.16 port 50186 ssh2
Dec  4 12:33:39 hosting sshd[27809]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.95.16  user=root
Dec  4 12:33:41 hosting sshd[27809]: Failed password for root from 217.182.95.16 port 45991 ssh2
...
2019-12-04 17:52:09
218.92.0.202 attackspambots
Dec  4 10:33:29 legacy sshd[13411]: Failed password for root from 218.92.0.202 port 43225 ssh2
Dec  4 10:35:36 legacy sshd[13525]: Failed password for root from 218.92.0.202 port 30267 ssh2
Dec  4 10:35:38 legacy sshd[13525]: Failed password for root from 218.92.0.202 port 30267 ssh2
...
2019-12-04 17:50:13
64.202.187.152 attackbots
Dec  3 23:42:38 auw2 sshd\[18460\]: Invalid user admin from 64.202.187.152
Dec  3 23:42:38 auw2 sshd\[18460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
Dec  3 23:42:40 auw2 sshd\[18460\]: Failed password for invalid user admin from 64.202.187.152 port 44764 ssh2
Dec  3 23:47:59 auw2 sshd\[18958\]: Invalid user ditthavong from 64.202.187.152
Dec  3 23:47:59 auw2 sshd\[18958\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.202.187.152
2019-12-04 17:59:46
170.254.26.43 attack
Fail2Ban Ban Triggered
2019-12-04 18:02:27
89.248.168.217 attackspambots
89.248.168.217 was recorded 21 times by 15 hosts attempting to connect to the following ports: 1284,1719. Incident counter (4h, 24h, all-time): 21, 196, 9120
2019-12-04 17:58:06

Recently Reported IPs

93.174.89.218 93.174.93.1 89.248.168.120 85.62.188.198
176.121.14.9 176.121.14.44 45.138.103.130 92.118.161.215
185.11.146.187 45.148.10.118 13.49.51.92 185.62.190.198
92.118.160.246 93.174.93.75 124.72.230.19 193.233.83.234
185.62.189.145 185.100.87.14 185.62.190.73 31.6.10.109