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

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

;; QUESTION SECTION:
;142.238.148.39.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 04:54:33 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 39.148.238.142.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 39.148.238.142.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
114.182.4.126 attackbots
(sshd) Failed SSH login from 114.182.4.126 (JP/Japan/i114-182-4-126.s42.a013.ap.plala.or.jp): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Aug 26 08:40:14 amsweb01 sshd[13323]: Invalid user eti from 114.182.4.126 port 61597
Aug 26 08:40:15 amsweb01 sshd[13323]: Failed password for invalid user eti from 114.182.4.126 port 61597 ssh2
Aug 26 08:49:34 amsweb01 sshd[15333]: Invalid user noreply from 114.182.4.126 port 62955
Aug 26 08:49:36 amsweb01 sshd[15333]: Failed password for invalid user noreply from 114.182.4.126 port 62955 ssh2
Aug 26 08:53:47 amsweb01 sshd[15888]: Invalid user x from 114.182.4.126 port 61733
2020-08-26 16:37:03
198.23.212.27 attack
$f2bV_matches
2020-08-26 16:10:35
122.51.125.104 attackbots
Aug 26 06:58:38 IngegnereFirenze sshd[7485]: Failed password for invalid user ec2-user from 122.51.125.104 port 60408 ssh2
...
2020-08-26 16:15:59
163.172.225.211 attackbotsspam
Aug 26 04:39:19 shivevps sshd[22415]: Bad protocol version identification '\024' from 163.172.225.211 port 50003
Aug 26 04:40:09 shivevps sshd[23711]: Bad protocol version identification '\024' from 163.172.225.211 port 33650
Aug 26 04:42:19 shivevps sshd[26427]: Bad protocol version identification '\024' from 163.172.225.211 port 50430
Aug 26 04:44:22 shivevps sshd[31178]: Bad protocol version identification '\024' from 163.172.225.211 port 56636
...
2020-08-26 15:55:49
74.97.19.201 attack
Aug 26 08:30:02 ns308116 sshd[5944]: Invalid user pi from 74.97.19.201 port 36954
Aug 26 08:30:02 ns308116 sshd[5945]: Invalid user pi from 74.97.19.201 port 36952
Aug 26 08:30:02 ns308116 sshd[5944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.97.19.201
Aug 26 08:30:02 ns308116 sshd[5945]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.97.19.201
Aug 26 08:30:05 ns308116 sshd[5944]: Failed password for invalid user pi from 74.97.19.201 port 36954 ssh2
Aug 26 08:30:05 ns308116 sshd[5945]: Failed password for invalid user pi from 74.97.19.201 port 36952 ssh2
...
2020-08-26 16:29:09
181.40.122.102 attackspam
Aug 26 04:37:18 shivevps sshd[18509]: Bad protocol version identification '\024' from 181.40.122.102 port 49240
Aug 26 04:38:56 shivevps sshd[21662]: Bad protocol version identification '\024' from 181.40.122.102 port 39751
Aug 26 04:42:21 shivevps sshd[26661]: Bad protocol version identification '\024' from 181.40.122.102 port 52400
...
2020-08-26 16:30:00
195.218.155.98 attackspambots
Aug 26 04:42:18 shivevps sshd[26418]: Bad protocol version identification '\024' from 195.218.155.98 port 56596
Aug 26 04:43:36 shivevps sshd[29507]: Bad protocol version identification '\024' from 195.218.155.98 port 57855
Aug 26 04:44:16 shivevps sshd[30874]: Bad protocol version identification '\024' from 195.218.155.98 port 58659
Aug 26 04:44:17 shivevps sshd[30887]: Bad protocol version identification '\024' from 195.218.155.98 port 58674
...
2020-08-26 15:54:05
94.26.87.55 attackspambots
Invalid user admin from 94.26.87.55 port 56866
2020-08-26 16:28:50
193.41.88.58 attackspambots
Aug 26 04:43:54 shivevps sshd[30191]: Bad protocol version identification '\024' from 193.41.88.58 port 42690
Aug 26 04:43:57 shivevps sshd[30309]: Bad protocol version identification '\024' from 193.41.88.58 port 42906
Aug 26 04:44:14 shivevps sshd[30751]: Bad protocol version identification '\024' from 193.41.88.58 port 43652
...
2020-08-26 16:11:01
122.176.65.143 attackspambots
Aug 26 04:43:34 shivevps sshd[29439]: Bad protocol version identification '\024' from 122.176.65.143 port 53930
Aug 26 04:43:53 shivevps sshd[30117]: Bad protocol version identification '\024' from 122.176.65.143 port 54661
Aug 26 04:43:53 shivevps sshd[30121]: Bad protocol version identification '\024' from 122.176.65.143 port 54663
Aug 26 04:43:54 shivevps sshd[30172]: Bad protocol version identification '\024' from 122.176.65.143 port 54703
...
2020-08-26 16:33:39
193.169.252.210 attackbotsspam
Aug 26 07:32:28 mail postfix/smtpd[90268]: warning: unknown[193.169.252.210]: SASL LOGIN authentication failed: generic failure
Aug 26 07:35:19 mail postfix/smtpd[90280]: warning: unknown[193.169.252.210]: SASL LOGIN authentication failed: generic failure
Aug 26 07:38:10 mail postfix/smtpd[90280]: warning: unknown[193.169.252.210]: SASL LOGIN authentication failed: generic failure
...
2020-08-26 15:54:39
23.129.64.187 attackspambots
$lgm
2020-08-26 15:56:38
106.12.207.236 attackbotsspam
Apr 16 16:46:31 ms-srv sshd[36788]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.207.236
Apr 16 16:46:34 ms-srv sshd[36788]: Failed password for invalid user og from 106.12.207.236 port 51032 ssh2
2020-08-26 15:51:46
163.172.198.72 attack
Aug 26 04:39:56 shivevps sshd[23372]: Bad protocol version identification '\024' from 163.172.198.72 port 60088
Aug 26 04:41:32 shivevps sshd[25747]: Bad protocol version identification '\024' from 163.172.198.72 port 36093
Aug 26 04:43:06 shivevps sshd[28735]: Bad protocol version identification '\024' from 163.172.198.72 port 38041
Aug 26 04:43:32 shivevps sshd[29288]: Bad protocol version identification '\024' from 163.172.198.72 port 36243
...
2020-08-26 16:35:35
190.90.18.170 attackspambots
Aug 26 04:37:41 shivevps sshd[19104]: Bad protocol version identification '\024' from 190.90.18.170 port 56942
Aug 26 04:38:17 shivevps sshd[20438]: Bad protocol version identification '\024' from 190.90.18.170 port 57386
Aug 26 04:43:53 shivevps sshd[30104]: Bad protocol version identification '\024' from 190.90.18.170 port 36569
...
2020-08-26 16:13:37

Recently Reported IPs

23.93.200.162 163.7.77.151 16.94.138.40 206.228.12.231
39.201.81.10 59.119.30.149 55.108.98.123 121.43.53.32
114.232.119.255 35.179.216.29 115.93.88.81 118.69.254.79
48.162.212.237 80.3.67.144 179.238.137.194 186.108.73.226
56.99.200.64 107.191.51.145 140.254.45.167 163.235.133.32