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

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

;; QUESTION SECTION:
;139.196.113.196.		IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:17:39 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 196.113.196.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 196.113.196.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
198.108.67.38 attack
ET DROP Dshield Block Listed Source group 1 - port: 9199 proto: TCP cat: Misc Attack
2020-03-12 22:24:04
129.204.205.125 attack
Invalid user ftptest from 129.204.205.125 port 52562
2020-03-12 22:23:16
175.195.254.99 attackbots
Mar 12 03:52:25 web9 sshd\[12284\]: Invalid user frappe from 175.195.254.99
Mar 12 03:52:25 web9 sshd\[12284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.195.254.99
Mar 12 03:52:27 web9 sshd\[12284\]: Failed password for invalid user frappe from 175.195.254.99 port 46228 ssh2
Mar 12 03:55:34 web9 sshd\[12780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.195.254.99  user=root
Mar 12 03:55:36 web9 sshd\[12780\]: Failed password for root from 175.195.254.99 port 42381 ssh2
2020-03-12 22:16:28
51.38.225.124 attack
Invalid user lby from 51.38.225.124 port 41018
2020-03-12 22:13:43
92.253.171.172 attackbots
suspicious action Thu, 12 Mar 2020 11:29:22 -0300
2020-03-12 22:54:04
49.70.60.168 attack
/auth/regist
2020-03-12 22:26:07
1.3.3.7 attackspambots
user from this ip was able to place fraud orders even after banning in wordpress
2020-03-12 22:20:36
185.176.27.190 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-03-12 22:53:23
96.81.178.35 attackbotsspam
2019-11-13T21:49:29.567Z CLOSE host=96.81.178.35 port=48784 fd=4 time=20.020 bytes=15
...
2020-03-12 22:22:43
109.239.49.168 attackspambots
suspicious action Thu, 12 Mar 2020 09:31:07 -0300
2020-03-12 22:15:11
36.72.218.107 attackspam
Unauthorized connection attempt from IP address 36.72.218.107 on Port 445(SMB)
2020-03-12 22:45:05
95.84.218.140 attack
2019-12-16T02:53:32.471Z CLOSE host=95.84.218.140 port=55155 fd=4 time=20.020 bytes=5
...
2020-03-12 22:31:29
113.162.172.131 attack
suspicious action Thu, 12 Mar 2020 09:30:47 -0300
2020-03-12 22:49:25
95.155.29.54 attackbots
2020-03-07T09:44:10.477Z CLOSE host=95.155.29.54 port=29449 fd=4 time=20.013 bytes=14
...
2020-03-12 22:39:43
83.97.20.37 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-03-12 22:34:21

Recently Reported IPs

139.196.113.117 139.196.112.23 139.196.113.79 139.196.120.217
139.196.115.48 139.196.120.52 139.196.113.73 139.196.120.102
118.24.90.160 139.196.113.94 139.196.120.157 139.196.121.216
139.196.121.239 139.196.121.152 139.196.120.209 139.196.122.17
139.196.122.190 139.196.122.166 139.196.123.142 118.24.90.186