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: Netherlands (the)

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.172.224.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1173
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;145.172.224.1.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 13:42:43 CST 2025
;; MSG SIZE  rcvd: 106
Host info
1.224.172.145.in-addr.arpa domain name pointer 145.172.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.62.244.194 attackspam
Nov 30 07:23:16 sachi sshd\[5745\]: Invalid user modular from 178.62.244.194
Nov 30 07:23:16 sachi sshd\[5745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.244.194
Nov 30 07:23:19 sachi sshd\[5745\]: Failed password for invalid user modular from 178.62.244.194 port 34807 ssh2
Nov 30 07:27:19 sachi sshd\[6052\]: Invalid user semper from 178.62.244.194
Nov 30 07:27:19 sachi sshd\[6052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.244.194
2019-12-01 06:21:52
106.241.16.119 attack
2019-11-30T16:53:51.4717111495-001 sshd\[33073\]: Invalid user hope from 106.241.16.119 port 46812
2019-11-30T16:53:51.4763381495-001 sshd\[33073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.241.16.119
2019-11-30T16:53:53.0211601495-001 sshd\[33073\]: Failed password for invalid user hope from 106.241.16.119 port 46812 ssh2
2019-11-30T17:08:51.2081321495-001 sshd\[33619\]: Invalid user admin from 106.241.16.119 port 37920
2019-11-30T17:08:51.2160021495-001 sshd\[33619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.241.16.119
2019-11-30T17:08:53.3177681495-001 sshd\[33619\]: Failed password for invalid user admin from 106.241.16.119 port 37920 ssh2
...
2019-12-01 06:42:54
49.88.112.75 attackspam
Nov 30 23:31:21 vps647732 sshd[9966]: Failed password for root from 49.88.112.75 port 38777 ssh2
...
2019-12-01 06:42:06
182.61.39.131 attackspam
Nov 30 18:47:09 odroid64 sshd\[11282\]: Invalid user dods from 182.61.39.131
Nov 30 18:47:09 odroid64 sshd\[11282\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.39.131
...
2019-12-01 06:07:19
150.109.116.241 attack
Automatic report - Banned IP Access
2019-12-01 06:11:15
62.173.154.20 attack
Fail2Ban Ban Triggered
2019-12-01 06:12:36
112.64.170.178 attackbots
2019-11-30T22:11:18.846048abusebot-3.cloudsearch.cf sshd\[17415\]: Invalid user treptow from 112.64.170.178 port 27753
2019-11-30T22:11:18.851733abusebot-3.cloudsearch.cf sshd\[17415\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.170.178
2019-12-01 06:27:40
87.120.36.237 attack
Nov 30 11:27:38 ws24vmsma01 sshd[89615]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.120.36.237
Nov 30 11:27:40 ws24vmsma01 sshd[89615]: Failed password for invalid user reedy from 87.120.36.237 port 5758 ssh2
...
2019-12-01 06:16:19
139.59.41.154 attackbots
Nov 30 22:10:08 srv-ubuntu-dev3 sshd[83984]: Invalid user us3r from 139.59.41.154
Nov 30 22:10:08 srv-ubuntu-dev3 sshd[83984]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Nov 30 22:10:08 srv-ubuntu-dev3 sshd[83984]: Invalid user us3r from 139.59.41.154
Nov 30 22:10:10 srv-ubuntu-dev3 sshd[83984]: Failed password for invalid user us3r from 139.59.41.154 port 53232 ssh2
Nov 30 22:13:59 srv-ubuntu-dev3 sshd[84326]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154  user=irc
Nov 30 22:14:00 srv-ubuntu-dev3 sshd[84326]: Failed password for irc from 139.59.41.154 port 55310 ssh2
Nov 30 22:17:53 srv-ubuntu-dev3 sshd[84616]: Invalid user eula from 139.59.41.154
Nov 30 22:17:53 srv-ubuntu-dev3 sshd[84616]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.41.154
Nov 30 22:17:53 srv-ubuntu-dev3 sshd[84616]: Invalid user eula from 139.59.41.154
...
2019-12-01 06:10:15
71.6.158.166 attackspam
71.6.158.166 was recorded 10 times by 9 hosts attempting to connect to the following ports: 4664,3306,4848,179,9943,3460,17000,49153,3310,23424. Incident counter (4h, 24h, all-time): 10, 48, 1184
2019-12-01 06:43:36
59.49.215.182 attackspambots
Portscan or hack attempt detected by psad/fwsnort
2019-12-01 06:24:14
37.49.229.168 attack
slow and persistent scanner
2019-12-01 06:36:36
121.142.111.222 attackbotsspam
SSH bruteforce (Triggered fail2ban)
2019-12-01 06:07:55
129.144.60.201 attack
Invalid user okawara from 129.144.60.201 port 56667
2019-12-01 06:20:49
41.164.195.204 attackbots
$f2bV_matches
2019-12-01 06:15:47

Recently Reported IPs

134.74.33.69 134.17.74.80 251.67.186.121 79.242.229.104
235.11.157.72 248.62.255.37 246.50.104.236 26.32.3.152
225.98.237.145 165.44.163.167 252.133.194.76 217.181.39.119
77.154.46.243 42.214.237.94 67.76.24.102 6.181.227.238
164.216.37.104 54.98.201.142 42.242.125.178 135.178.63.230