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

;; QUESTION SECTION:
;139.196.217.210.		IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:19:38 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 210.217.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 210.217.196.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
202.88.241.107 attackbotsspam
Invalid user user from 202.88.241.107 port 48142
2019-10-03 20:02:56
118.25.210.180 attackbotsspam
$f2bV_matches
2019-10-03 19:41:54
132.232.182.190 attackbots
2019-08-22 08:03:07,081 fail2ban.actions        [878]: NOTICE  [sshd] Ban 132.232.182.190
2019-08-22 11:09:33,062 fail2ban.actions        [878]: NOTICE  [sshd] Ban 132.232.182.190
2019-08-22 14:17:25,135 fail2ban.actions        [878]: NOTICE  [sshd] Ban 132.232.182.190
...
2019-10-03 19:45:00
118.25.190.181 attack
$f2bV_matches
2019-10-03 19:51:35
118.25.14.51 attackspambots
$f2bV_matches
2019-10-03 19:59:11
131.0.245.4 attackbots
2019-08-25 23:08:16,035 fail2ban.actions        [878]: NOTICE  [sshd] Ban 131.0.245.4
2019-08-26 02:16:55,112 fail2ban.actions        [878]: NOTICE  [sshd] Ban 131.0.245.4
2019-08-26 05:33:20,068 fail2ban.actions        [878]: NOTICE  [sshd] Ban 131.0.245.4
...
2019-10-03 20:12:42
68.183.94.194 attackspam
Oct  3 10:37:02 fr01 sshd[27913]: Invalid user mc from 68.183.94.194
Oct  3 10:37:02 fr01 sshd[27913]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.94.194
Oct  3 10:37:02 fr01 sshd[27913]: Invalid user mc from 68.183.94.194
Oct  3 10:37:05 fr01 sshd[27913]: Failed password for invalid user mc from 68.183.94.194 port 39178 ssh2
...
2019-10-03 19:39:53
118.25.129.11 attackspambots
$f2bV_matches
2019-10-03 20:03:14
37.49.231.104 attack
10/03/2019-11:51:13.687319 37.49.231.104 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 35
2019-10-03 20:16:08
93.190.217.9 attack
SASL Brute Force
2019-10-03 19:42:56
118.25.191.151 attackspambots
$f2bV_matches
2019-10-03 19:49:12
132.232.39.15 attackbotsspam
Automatic report - Banned IP Access
2019-10-03 19:35:58
94.102.53.52 attackspambots
Oct  3 00:07:11 plusreed sshd[11306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.102.53.52  user=postgres
Oct  3 00:07:13 plusreed sshd[11306]: Failed password for postgres from 94.102.53.52 port 39090 ssh2
...
2019-10-03 19:44:12
118.25.224.157 attackbotsspam
$f2bV_matches
2019-10-03 19:38:42
130.61.88.225 attackspam
Automatic report - Banned IP Access
2019-10-03 20:19:50

Recently Reported IPs

139.196.217.93 139.196.218.177 139.196.218.147 139.196.218.200
139.196.218.2 118.244.131.171 139.196.218.204 139.196.218.218
139.196.218.54 139.196.218.65 139.196.218.77 139.196.218.71
139.196.218.83 139.196.218.89 139.196.218.95 139.196.219.144
139.196.219.153 139.196.219.166 139.196.219.199 139.196.219.147