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

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

;; QUESTION SECTION:
;1.10.138.21.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 24 10:08:14 CST 2022
;; MSG SIZE  rcvd: 104
Host info
21.138.10.1.in-addr.arpa domain name pointer node-1zp.pool-1-10.dynamic.totinternet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.138.10.1.in-addr.arpa	name = node-1zp.pool-1-10.dynamic.totinternet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.74.123.83 attackspambots
SSH Brute Force
2019-08-02 04:22:05
42.114.30.227 attackspam
Autoban   42.114.30.227 AUTH/CONNECT
2019-08-02 04:57:19
101.201.75.140 attackbotsspam
Aug  1 14:16:57 localhost sshd\[20369\]: Invalid user ts3user from 101.201.75.140 port 48563
Aug  1 14:16:58 localhost sshd\[20369\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.201.75.140
Aug  1 14:17:00 localhost sshd\[20369\]: Failed password for invalid user ts3user from 101.201.75.140 port 48563 ssh2
Aug  1 14:17:37 localhost sshd\[20391\]: Invalid user mailnull from 101.201.75.140 port 50777
2019-08-02 04:24:33
31.132.248.90 attack
Automatic report - Port Scan Attack
2019-08-02 04:38:41
212.47.250.50 attack
SSH Brute-Force attacks
2019-08-02 04:52:51
198.27.74.64 attackbots
blogonese.net 198.27.74.64 \[01/Aug/2019:19:49:41 +0200\] "POST /wp-login.php HTTP/1.1" 200 5771 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
blogonese.net 198.27.74.64 \[01/Aug/2019:19:49:42 +0200\] "POST /wp-login.php HTTP/1.1" 200 5770 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-08-02 04:32:36
181.139.54.231 attackspam
Automatic report - Port Scan Attack
2019-08-02 04:21:32
95.91.214.40 attackbotsspam
ENG,WP GET /wp-login.php
2019-08-02 04:28:03
54.38.33.186 attackbotsspam
$f2bV_matches
2019-08-02 04:48:54
46.101.224.184 attackspam
Aug  1 20:35:40 mail sshd\[8354\]: Failed password for invalid user se from 46.101.224.184 port 58244 ssh2
Aug  1 20:54:04 mail sshd\[8663\]: Invalid user ftptest from 46.101.224.184 port 36970
Aug  1 20:54:04 mail sshd\[8663\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.224.184
...
2019-08-02 05:05:15
206.81.4.235 attack
Aug  1 18:15:30 server sshd[11781]: Failed password for invalid user jenkins from 206.81.4.235 port 48858 ssh2
Aug  1 18:21:29 server sshd[12246]: Failed password for invalid user lilli from 206.81.4.235 port 56898 ssh2
Aug  1 18:25:27 server sshd[12616]: Failed password for invalid user sylee from 206.81.4.235 port 53893 ssh2
2019-08-02 04:39:52
58.213.166.140 attackspam
Automated report - ssh fail2ban:
Aug 1 21:42:23 authentication failure 
Aug 1 21:42:25 wrong password, user=my, port=44170, ssh2
Aug 1 22:13:50 authentication failure
2019-08-02 04:40:50
160.16.148.109 attackspambots
SSH/22 MH Probe, BF, Hack -
2019-08-02 04:39:05
211.75.194.80 attackbots
Automated report - ssh fail2ban:
Aug 1 15:16:56 wrong password, user=phillip, port=40288, ssh2
Aug 1 15:51:36 authentication failure 
Aug 1 15:51:38 wrong password, user=123456, port=60994, ssh2
2019-08-02 04:47:08
191.53.236.126 attackspambots
Aug  1 08:17:34 mailman postfix/smtpd[9955]: warning: unknown[191.53.236.126]: SASL PLAIN authentication failed: authentication failure
2019-08-02 04:26:03

Recently Reported IPs

1.10.138.201 1.10.138.219 1.10.138.221 1.10.138.224
1.10.138.228 1.10.138.236 1.10.138.247 1.10.138.248
1.10.138.26 178.19.134.163 1.10.138.28 1.10.138.35
1.10.138.39 1.10.138.40 1.10.138.46 250.75.100.250
1.10.138.49 1.10.138.54 1.10.138.56 1.10.138.6