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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.138.38.198
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56923
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.138.38.198.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 28 01:58:54 CST 2022
;; MSG SIZE  rcvd: 107
Host info
198.38.138.139.in-addr.arpa is an alias for 198.38.138.139.in-addr.arpa.iphmx.com.
198.38.138.139.in-addr.arpa.iphmx.com domain name pointer esa2.hc3677-93.iphmx.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
198.38.138.139.in-addr.arpa	canonical name = 198.38.138.139.in-addr.arpa.iphmx.com.
198.38.138.139.in-addr.arpa.iphmx.com	name = esa2.hc3677-93.iphmx.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
119.96.159.71 attack
$f2bV_matches
2020-04-10 09:52:35
49.87.171.23 attackbots
(smtpauth) Failed SMTP AUTH login from 49.87.171.23 (CN/China/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-04-10 02:23:42 plain authenticator failed for (54bf329a06.wellweb.host) [49.87.171.23]: 535 Incorrect authentication data (set_id=info@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com@fardineh.com)
2020-04-10 09:23:44
54.36.54.24 attack
Apr 10 00:13:57 vmd26974 sshd[25763]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.54.24
Apr 10 00:14:00 vmd26974 sshd[25763]: Failed password for invalid user jatten from 54.36.54.24 port 39628 ssh2
...
2020-04-10 09:53:33
164.132.225.151 attackbots
(sshd) Failed SSH login from 164.132.225.151 (FR/France/151.ip-164-132-225.eu): 5 in the last 3600 secs
2020-04-10 09:41:23
129.211.104.34 attackbotsspam
Apr 10 00:50:55 icinga sshd[34692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.104.34 
Apr 10 00:50:57 icinga sshd[34692]: Failed password for invalid user discover from 129.211.104.34 port 59966 ssh2
Apr 10 00:58:07 icinga sshd[45796]: Failed password for root from 129.211.104.34 port 42006 ssh2
...
2020-04-10 09:22:29
45.14.150.103 attack
Apr  9 21:13:04 ny01 sshd[21645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.14.150.103
Apr  9 21:13:07 ny01 sshd[21645]: Failed password for invalid user ubuntu from 45.14.150.103 port 50836 ssh2
Apr  9 21:21:44 ny01 sshd[22628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.14.150.103
2020-04-10 09:37:30
51.89.213.90 attackbotsspam
Automatic report - XMLRPC Attack
2020-04-10 09:19:09
222.186.15.62 attackspambots
(sshd) Failed SSH login from 222.186.15.62 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 10 02:56:37 amsweb01 sshd[12358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.62  user=root
Apr 10 02:56:39 amsweb01 sshd[12358]: Failed password for root from 222.186.15.62 port 25418 ssh2
Apr 10 02:56:40 amsweb01 sshd[12358]: Failed password for root from 222.186.15.62 port 25418 ssh2
Apr 10 02:56:42 amsweb01 sshd[12358]: Failed password for root from 222.186.15.62 port 25418 ssh2
Apr 10 03:52:53 amsweb01 sshd[22692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.62  user=root
2020-04-10 09:54:08
185.176.222.99 attack
" "
2020-04-10 09:22:02
23.97.51.25 attackbotsspam
Apr 10 00:47:21 server sshd[2010]: Failed password for invalid user postgres from 23.97.51.25 port 1024 ssh2
Apr 10 00:51:45 server sshd[3153]: Failed password for invalid user test from 23.97.51.25 port 1024 ssh2
Apr 10 00:56:14 server sshd[4167]: Failed password for invalid user production from 23.97.51.25 port 1024 ssh2
2020-04-10 09:48:35
118.24.158.42 attackspam
Apr  9 22:55:13 scw-6657dc sshd[12333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.158.42
Apr  9 22:55:13 scw-6657dc sshd[12333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.158.42
Apr  9 22:55:15 scw-6657dc sshd[12333]: Failed password for invalid user elasticsearch from 118.24.158.42 port 47842 ssh2
...
2020-04-10 09:45:48
210.99.216.205 attackspambots
SSH brute force attempt
2020-04-10 09:34:12
167.114.144.96 attackbotsspam
Apr 10 00:45:27 powerpi2 sshd[9472]: Invalid user ubuntu from 167.114.144.96 port 56290
Apr 10 00:45:29 powerpi2 sshd[9472]: Failed password for invalid user ubuntu from 167.114.144.96 port 56290 ssh2
Apr 10 00:52:45 powerpi2 sshd[9888]: Invalid user test from 167.114.144.96 port 48712
...
2020-04-10 09:29:16
125.212.233.50 attack
$lgm
2020-04-10 09:51:14
122.224.232.66 attackbots
SSH-BruteForce
2020-04-10 09:30:20

Recently Reported IPs

139.138.46.127 59.1.5.196 139.138.39.91 153.4.181.149
139.138.39.92 95.94.75.74 58.140.24.218 50.191.50.156
128.177.236.99 226.179.223.4 91.185.78.171 248.90.122.174
72.152.82.208 217.194.66.216 237.21.211.109 247.221.182.207
79.19.229.246 242.100.11.66 247.31.207.169 48.198.32.221