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

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
138.122.20.255 attackbots
Automatic report - Port Scan Attack
2020-05-21 22:24:10
138.122.20.93 attackbotsspam
DATE:2020-05-13 14:34:32, IP:138.122.20.93, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-05-14 01:44:14
138.122.202.200 attack
fail2ban
2020-04-12 22:29:28
138.122.202.200 attackspambots
(sshd) Failed SSH login from 138.122.202.200 (CO/Colombia/Departamento del Valle del Cauca/Buenaventura/dsl-emcali-138.122.202.200.emcali.net.co/[AS10299 EMPRESAS MUNICIPALES DE CALI E.I.C.E. E.S.P.]): 1 in the last 3600 secs
2020-04-09 06:43:42
138.122.202.200 attackspam
Mar  1 14:16:45 MK-Soft-VM7 sshd[4915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.122.202.200 
Mar  1 14:16:47 MK-Soft-VM7 sshd[4915]: Failed password for invalid user andoria from 138.122.202.200 port 48186 ssh2
...
2020-03-02 05:09:52
138.122.20.74 attack
unauthorized connection attempt
2020-02-07 17:58:12
138.122.20.81 attack
Unauthorized connection attempt detected from IP address 138.122.20.81 to port 80 [J]
2020-01-25 16:04:02
138.122.202.200 attack
$f2bV_matches
2020-01-10 06:28:23
138.122.202.200 attack
Unauthorized connection attempt detected from IP address 138.122.202.200 to port 2220 [J]
2020-01-07 18:22:46
138.122.202.200 attackspam
Unauthorized connection attempt detected from IP address 138.122.202.200 to port 2220 [J]
2020-01-04 22:52:13
138.122.20.79 attackspam
Automatic report - Port Scan Attack
2019-12-21 07:18:16
138.122.20.5 attackspambots
Honeypot attack, port: 445, PTR: 138-122-20-5.rminet.com.br.
2019-11-27 20:44:54
138.122.20.5 attackbots
1433/tcp 1433/tcp 445/tcp
[2019-10-09/11-15]3pkt
2019-11-16 08:30:49
138.122.20.95 attack
19/11/12@09:40:45: FAIL: IoT-Telnet address from=138.122.20.95
...
2019-11-12 23:52:23
138.122.202.200 attackbots
2019-11-06T08:52:08.991770abusebot-5.cloudsearch.cf sshd\[5455\]: Invalid user hirano from 138.122.202.200 port 36430
2019-11-06 20:47:39
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.122.20.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37431
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.122.20.80.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 20:47:40 CST 2022
;; MSG SIZE  rcvd: 106
Host info
b'80.20.122.138.in-addr.arpa domain name pointer 138-122-20-80.rminet.com.br.
'
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.20.122.138.in-addr.arpa	name = 138-122-20-80.rminet.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
59.152.62.189 attackspam
Apr 30 23:13:52 pixelmemory sshd[3963]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.152.62.189
Apr 30 23:13:55 pixelmemory sshd[3963]: Failed password for invalid user wk from 59.152.62.189 port 52540 ssh2
Apr 30 23:25:31 pixelmemory sshd[6485]: Failed password for root from 59.152.62.189 port 57700 ssh2
...
2020-05-01 15:53:58
129.28.166.61 attackbots
ssh brute force
2020-05-01 15:43:14
175.142.67.242 attackbots
Time:     Fri May  1 00:31:17 2020 -0300
IP:       175.142.67.242 (MY/Malaysia/-)
Failures: 20 (WordPressBruteForcePOST)
Interval: 3600 seconds
Blocked:  Permanent Block
2020-05-01 15:38:52
148.70.154.10 attackbotsspam
2020-05-01T04:19:45.807973abusebot-8.cloudsearch.cf sshd[32599]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.154.10  user=root
2020-05-01T04:19:48.038685abusebot-8.cloudsearch.cf sshd[32599]: Failed password for root from 148.70.154.10 port 43494 ssh2
2020-05-01T04:24:39.412831abusebot-8.cloudsearch.cf sshd[473]: Invalid user fram from 148.70.154.10 port 54104
2020-05-01T04:24:39.419099abusebot-8.cloudsearch.cf sshd[473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.154.10
2020-05-01T04:24:39.412831abusebot-8.cloudsearch.cf sshd[473]: Invalid user fram from 148.70.154.10 port 54104
2020-05-01T04:24:41.343546abusebot-8.cloudsearch.cf sshd[473]: Failed password for invalid user fram from 148.70.154.10 port 54104 ssh2
2020-05-01T04:29:25.618822abusebot-8.cloudsearch.cf sshd[725]: Invalid user jim from 148.70.154.10 port 36482
...
2020-05-01 16:14:23
211.169.234.55 attack
Invalid user esc from 211.169.234.55 port 33712
2020-05-01 16:02:30
176.28.19.179 attackbots
<6 unauthorized SSH connections
2020-05-01 15:38:31
49.232.131.80 attack
Apr 30 19:43:14 kapalua sshd\[3615\]: Invalid user ck from 49.232.131.80
Apr 30 19:43:14 kapalua sshd\[3615\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.131.80
Apr 30 19:43:16 kapalua sshd\[3615\]: Failed password for invalid user ck from 49.232.131.80 port 40526 ssh2
Apr 30 19:47:24 kapalua sshd\[4059\]: Invalid user postgres from 49.232.131.80
Apr 30 19:47:24 kapalua sshd\[4059\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.131.80
2020-05-01 15:57:58
134.175.190.226 attackspam
2020-05-01T07:02:04.350368abusebot-3.cloudsearch.cf sshd[14214]: Invalid user wyy from 134.175.190.226 port 35042
2020-05-01T07:02:04.360152abusebot-3.cloudsearch.cf sshd[14214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.190.226
2020-05-01T07:02:04.350368abusebot-3.cloudsearch.cf sshd[14214]: Invalid user wyy from 134.175.190.226 port 35042
2020-05-01T07:02:06.920464abusebot-3.cloudsearch.cf sshd[14214]: Failed password for invalid user wyy from 134.175.190.226 port 35042 ssh2
2020-05-01T07:07:17.285711abusebot-3.cloudsearch.cf sshd[14510]: Invalid user dev from 134.175.190.226 port 35294
2020-05-01T07:07:17.291905abusebot-3.cloudsearch.cf sshd[14510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.190.226
2020-05-01T07:07:17.285711abusebot-3.cloudsearch.cf sshd[14510]: Invalid user dev from 134.175.190.226 port 35294
2020-05-01T07:07:19.154709abusebot-3.cloudsearch.cf sshd[14510]: Fa
...
2020-05-01 15:42:28
13.76.85.10 attackspambots
Invalid user sk from 13.76.85.10 port 33626
2020-05-01 16:00:09
102.68.17.48 attackbots
Invalid user yh from 102.68.17.48 port 52032
2020-05-01 15:50:49
59.80.40.147 attack
Invalid user testuser1 from 59.80.40.147 port 53134
2020-05-01 15:54:16
140.206.242.83 attackbotsspam
May  1 07:46:37 raspberrypi sshd\[664\]: Failed password for root from 140.206.242.83 port 47378 ssh2May  1 08:00:35 raspberrypi sshd\[8608\]: Invalid user bhq from 140.206.242.83May  1 08:00:38 raspberrypi sshd\[8608\]: Failed password for invalid user bhq from 140.206.242.83 port 39223 ssh2
...
2020-05-01 16:14:56
122.166.237.117 attackspam
[Aegis] @ 2019-12-11 06:19:27  0100 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2020-05-01 16:20:25
180.89.58.27 attackspambots
hit -> srv3:22
2020-05-01 16:07:12
47.90.75.80 attackbotsspam
Invalid user ben from 47.90.75.80 port 56560
2020-05-01 15:58:34

Recently Reported IPs

194.88.225.68 123.245.25.20 162.12.211.74 69.21.2.144
46.99.251.125 80.28.102.26 62.210.215.118 80.15.39.135
27.120.1.39 183.216.234.215 185.64.47.98 167.249.102.164
114.96.218.231 113.246.252.183 71.103.113.102 125.43.83.203
103.15.242.216 179.171.12.243 156.241.132.63 132.248.215.17