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

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
189.213.138.7 attack
Automatic report - Port Scan Attack
2020-04-22 06:39:58
189.213.138.224 attack
*Port Scan* detected from 189.213.138.224 (MX/Mexico/-). 4 hits in the last 60 seconds
2019-11-21 18:43:15
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 189.213.138.22
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32901
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;189.213.138.22.			IN	A

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

;; Query time: 52 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 15:31:11 CST 2022
;; MSG SIZE  rcvd: 107
Host info
22.138.213.189.in-addr.arpa domain name pointer 189-213-138-22.static.axtel.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
22.138.213.189.in-addr.arpa	name = 189-213-138-22.static.axtel.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
138.197.171.124 attackbotsspam
Jun 30 15:13:44 localhost sshd\[24644\]: Invalid user ts3srv from 138.197.171.124
Jun 30 15:13:44 localhost sshd\[24644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.171.124
Jun 30 15:13:45 localhost sshd\[24644\]: Failed password for invalid user ts3srv from 138.197.171.124 port 41521 ssh2
Jun 30 15:15:46 localhost sshd\[24822\]: Invalid user apache from 138.197.171.124
Jun 30 15:15:46 localhost sshd\[24822\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.171.124
...
2019-07-01 04:18:28
223.19.110.34 attack
TCP port 445 (SMB) attempt blocked by firewall. [2019-06-30 15:14:14]
2019-07-01 04:25:28
54.39.96.8 attack
Jun 30 21:46:00 cp sshd[19512]: Failed password for mysql from 54.39.96.8 port 34244 ssh2
Jun 30 21:46:00 cp sshd[19512]: Failed password for mysql from 54.39.96.8 port 34244 ssh2
2019-07-01 04:39:32
5.196.110.170 attackspam
SSH bruteforce (Triggered fail2ban)
2019-07-01 04:22:33
109.123.117.243 attackbots
7011/tcp 8545/tcp 7547/tcp...
[2019-05-01/06-30]12pkt,9pt.(tcp),3pt.(udp)
2019-07-01 04:28:39
85.14.245.157 attack
3389BruteforceFW22
2019-07-01 03:59:03
42.228.200.90 attack
port scan and connect, tcp 23 (telnet)
2019-07-01 04:14:50
190.152.124.134 attackspambots
proto=tcp  .  spt=48456  .  dpt=25  .     (listed on Blocklist de  Jun 29)     (771)
2019-07-01 04:09:59
202.71.14.103 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2019-07-01 04:21:01
209.16.78.27 attack
SPF Fail sender not permitted to send mail for @123.net / Mail sent to address obtained from MySpace hack
2019-07-01 04:40:52
79.180.62.226 attack
php WP PHPmyadamin ABUSE blocked for 12h
2019-07-01 04:02:07
185.36.81.168 attack
Rude login attack (16 tries in 1d)
2019-07-01 03:58:10
158.69.192.147 attack
SSH bruteforce
2019-07-01 04:15:19
45.71.31.4 attackspam
proto=tcp  .  spt=39534  .  dpt=25  .     (listed on     Github Combined on 3 lists )     (764)
2019-07-01 04:34:29
88.202.190.143 attackbotsspam
7678/tcp 5555/tcp 8883/tcp...
[2019-05-01/06-30]4pkt,4pt.(tcp)
2019-07-01 04:01:11

Recently Reported IPs

124.11.208.20 113.111.213.88 82.151.123.232 187.162.170.159
117.175.114.144 111.202.167.25 177.249.171.85 94.255.247.248
146.70.29.180 190.109.236.105 113.89.7.190 200.12.30.237
14.21.5.8 185.138.230.68 23.108.42.82 213.22.202.130
167.99.76.115 109.120.23.38 207.134.191.40 144.168.241.9