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: United States

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
174.138.42.143 attackbots
DATE:2020-09-20 15:49:05,IP:174.138.42.143,MATCHES:10,PORT:ssh
2020-09-20 22:28:49
174.138.42.143 attackbotsspam
firewall-block, port(s): 29183/tcp
2020-09-20 14:20:11
174.138.42.143 attackbotsspam
Invalid user suser from 174.138.42.143 port 53068
2020-09-20 06:19:38
174.138.42.143 attackspam
Invalid user admin from 174.138.42.143 port 35190
2020-08-23 05:33:28
174.138.42.143 attackbotsspam
Aug 21 14:38:37 abendstille sshd\[17124\]: Invalid user ubuntu from 174.138.42.143
Aug 21 14:38:37 abendstille sshd\[17124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143
Aug 21 14:38:40 abendstille sshd\[17124\]: Failed password for invalid user ubuntu from 174.138.42.143 port 41806 ssh2
Aug 21 14:43:18 abendstille sshd\[21525\]: Invalid user lazaro from 174.138.42.143
Aug 21 14:43:18 abendstille sshd\[21525\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143
...
2020-08-21 20:54:23
174.138.42.143 attack
Aug 15 15:11:25 journals sshd\[103829\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143  user=root
Aug 15 15:11:27 journals sshd\[103829\]: Failed password for root from 174.138.42.143 port 58914 ssh2
Aug 15 15:16:02 journals sshd\[104244\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143  user=root
Aug 15 15:16:04 journals sshd\[104244\]: Failed password for root from 174.138.42.143 port 38464 ssh2
Aug 15 15:20:20 journals sshd\[104618\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143  user=root
...
2020-08-16 00:26:03
174.138.42.143 attack
Aug  7 06:52:27 ovpn sshd\[32736\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143  user=root
Aug  7 06:52:29 ovpn sshd\[32736\]: Failed password for root from 174.138.42.143 port 48568 ssh2
Aug  7 07:05:18 ovpn sshd\[5314\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143  user=root
Aug  7 07:05:20 ovpn sshd\[5314\]: Failed password for root from 174.138.42.143 port 34304 ssh2
Aug  7 07:07:23 ovpn sshd\[6145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.42.143  user=root
2020-08-07 13:17:39
174.138.42.143 attack
$f2bV_matches
2020-08-05 15:38:50
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 174.138.42.86
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16946
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;174.138.42.86.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 14 21:49:21 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 86.42.138.174.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 86.42.138.174.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.13.39.232 attackspambots
Unauthorized connection attempt detected from IP address 106.13.39.232 to port 23 [T]
2020-01-10 08:28:52
222.82.57.105 attackspambots
Unauthorized connection attempt detected from IP address 222.82.57.105 to port 81 [T]
2020-01-10 08:36:51
124.90.52.189 attack
Unauthorized connection attempt detected from IP address 124.90.52.189 to port 82 [T]
2020-01-10 08:46:03
119.39.46.250 attackspambots
Unauthorized connection attempt detected from IP address 119.39.46.250 to port 82 [T]
2020-01-10 08:22:27
123.145.38.177 attackspam
Unauthorized connection attempt detected from IP address 123.145.38.177 to port 8118 [T]
2020-01-10 08:20:46
60.216.139.111 attack
Unauthorized connection attempt detected from IP address 60.216.139.111 to port 80 [T]
2020-01-10 08:30:16
113.120.8.54 attack
Unauthorized connection attempt detected from IP address 113.120.8.54 to port 8899 [T]
2020-01-10 08:24:50
223.166.75.15 attack
Unauthorized connection attempt detected from IP address 223.166.75.15 to port 83 [T]
2020-01-10 08:35:31
120.76.123.100 attack
Unauthorized connection attempt detected from IP address 120.76.123.100 to port 1433 [T]
2020-01-10 08:22:09
111.224.235.108 attack
Unauthorized connection attempt detected from IP address 111.224.235.108 to port 80 [T]
2020-01-10 08:26:27
111.224.235.71 attack
Unauthorized connection attempt detected from IP address 111.224.235.71 to port 80 [T]
2020-01-10 08:27:01
116.252.0.11 attackspam
Unauthorized connection attempt detected from IP address 116.252.0.11 to port 8080 [T]
2020-01-10 08:53:08
116.252.0.18 attack
Unauthorized connection attempt detected from IP address 116.252.0.18 to port 8001 [T]
2020-01-10 08:52:37
221.13.12.25 attack
Unauthorized connection attempt detected from IP address 221.13.12.25 to port 9991 [T]
2020-01-10 08:38:58
124.235.138.245 attack
Unauthorized connection attempt detected from IP address 124.235.138.245 to port 82 [T]
2020-01-10 08:44:44

Recently Reported IPs

41.60.235.75 5.188.64.251 173.185.7.125 160.248.16.148
170.231.55.39 171.6.10.57 144.168.148.168 77.83.86.232
85.208.210.42 24.69.34.20 45.66.209.88 183.78.133.27
52.229.96.231 54.90.126.16 115.144.175.156 49.213.214.54
113.162.1.233 176.31.249.138 178.174.198.23 186.211.6.137