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

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

;; QUESTION SECTION:
;145.150.74.238.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Dec 30 17:21:33 CST 2022
;; MSG SIZE  rcvd: 107
Host info
238.74.150.145.in-addr.arpa domain name pointer 145.150.EARLY-REGISTRATION.of.SURFnet.invalid.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
92.118.37.86 attackbots
firewall-block, port(s): 321/tcp, 7791/tcp, 9311/tcp, 9381/tcp
2019-07-06 06:35:34
125.212.254.144 attackbots
Tried sshing with brute force.
2019-07-06 06:21:22
142.93.240.141 attack
WordPress wp-login brute force :: 142.93.240.141 0.060 BYPASS [06/Jul/2019:07:00:48  1000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-06 06:50:29
177.44.16.125 attackspam
Unauthorized connection attempt from IP address 177.44.16.125 on Port 587(SMTP-MSA)
2019-07-06 06:44:20
217.62.238.199 attack
Automatic report - Web App Attack
2019-07-06 06:31:20
104.131.93.33 attackspam
Jul  6 03:08:13 tanzim-HP-Z238-Microtower-Workstation sshd\[24354\]: Invalid user npmaseko from 104.131.93.33
Jul  6 03:08:13 tanzim-HP-Z238-Microtower-Workstation sshd\[24354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.93.33
Jul  6 03:08:15 tanzim-HP-Z238-Microtower-Workstation sshd\[24354\]: Failed password for invalid user npmaseko from 104.131.93.33 port 42978 ssh2
...
2019-07-06 06:52:53
140.246.124.56 attackbotsspam
scan z
2019-07-06 06:41:27
223.97.176.169 attack
TCP port 23 (Telnet) attempt blocked by firewall. [2019-07-05 20:00:39]
2019-07-06 06:30:26
202.83.168.108 attackspambots
Unauthorized connection attempt from IP address 202.83.168.108 on Port 445(SMB)
2019-07-06 06:45:42
141.98.81.38 attack
Jul  6 04:05:23 lcl-usvr-01 sshd[2550]: Invalid user admin from 141.98.81.38
2019-07-06 06:18:21
49.83.174.185 attack
21/tcp 21/tcp 21/tcp...
[2019-07-03/05]4pkt,1pt.(tcp)
2019-07-06 06:38:08
140.249.198.245 attackspam
$f2bV_matches
2019-07-06 06:42:31
24.2.205.235 attack
[AUTOMATIC REPORT] - 21 tries in total - SSH BRUTE FORCE - IP banned
2019-07-06 06:39:37
218.92.0.134 attackbots
Jul  5 22:12:46 s64-1 sshd[10318]: Failed password for root from 218.92.0.134 port 14648 ssh2
Jul  5 22:12:49 s64-1 sshd[10318]: Failed password for root from 218.92.0.134 port 14648 ssh2
Jul  5 22:13:00 s64-1 sshd[10318]: error: maximum authentication attempts exceeded for root from 218.92.0.134 port 14648 ssh2 [preauth]
...
2019-07-06 06:18:53
180.76.155.227 attack
993
2019-07-06 06:13:07

Recently Reported IPs

145.178.35.88 144.187.230.226 144.159.33.1 143.70.111.69
143.228.73.151 143.21.139.249 143.249.67.127 142.99.116.93
142.34.48.60 142.178.28.239 142.116.139.172 253.232.86.118
141.56.10.177 141.69.64.195 141.31.81.252 141.219.160.144
141.148.129.97 141.185.202.193 140.73.61.125 140.233.173.154