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: United States

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

;; QUESTION SECTION:
;18.138.252.221.			IN	A

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

;; Query time: 95 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 18:46:48 CST 2022
;; MSG SIZE  rcvd: 107
Host info
221.252.138.18.in-addr.arpa domain name pointer ec2-18-138-252-221.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
221.252.138.18.in-addr.arpa	name = ec2-18-138-252-221.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.23.35 attackspam
Nov 14 07:25:34 xeon sshd[60484]: Failed password for invalid user ftp from 106.13.23.35 port 38972 ssh2
2019-11-14 16:41:49
193.164.205.35 attack
SSH Brute-Force reported by Fail2Ban
2019-11-14 16:54:02
112.44.238.93 attackbots
Fail2Ban Ban Triggered
2019-11-14 17:17:00
115.54.215.16 attackspambots
UTC: 2019-11-13 port: 23/tcp
2019-11-14 16:40:02
14.252.246.236 attackbotsspam
Automatic report - Port Scan Attack
2019-11-14 17:10:50
104.37.169.192 attackbots
2019-11-14T06:27:29.831060abusebot-8.cloudsearch.cf sshd\[7943\]: Invalid user iemanja from 104.37.169.192 port 49276
2019-11-14 17:07:08
138.197.145.26 attackbots
Nov 14 08:29:46 MK-Soft-VM8 sshd[25415]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.145.26 
Nov 14 08:29:48 MK-Soft-VM8 sshd[25415]: Failed password for invalid user access123 from 138.197.145.26 port 41220 ssh2
...
2019-11-14 16:50:35
31.210.65.150 attackbots
Nov 14 10:41:43 pkdns2 sshd\[43607\]: Invalid user qwerty from 31.210.65.150Nov 14 10:41:45 pkdns2 sshd\[43607\]: Failed password for invalid user qwerty from 31.210.65.150 port 43625 ssh2Nov 14 10:45:41 pkdns2 sshd\[43760\]: Invalid user area51 from 31.210.65.150Nov 14 10:45:43 pkdns2 sshd\[43760\]: Failed password for invalid user area51 from 31.210.65.150 port 33419 ssh2Nov 14 10:49:29 pkdns2 sshd\[43868\]: Invalid user lepianka from 31.210.65.150Nov 14 10:49:31 pkdns2 sshd\[43868\]: Failed password for invalid user lepianka from 31.210.65.150 port 51455 ssh2
...
2019-11-14 17:05:17
142.93.47.171 attackspam
Automatic report - XMLRPC Attack
2019-11-14 17:16:22
112.80.54.62 attack
Nov 14 07:27:36 MK-Soft-Root2 sshd[21938]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.80.54.62 
Nov 14 07:27:37 MK-Soft-Root2 sshd[21938]: Failed password for invalid user kibria from 112.80.54.62 port 51792 ssh2
...
2019-11-14 16:58:08
185.193.176.203 attack
Dovecot Brute-Force
2019-11-14 16:51:30
37.79.134.196 attackbots
Chat Spam
2019-11-14 17:08:21
190.9.130.159 attackspam
2019-11-14T08:55:56.441048abusebot-6.cloudsearch.cf sshd\[30941\]: Invalid user cl from 190.9.130.159 port 60609
2019-11-14 17:14:50
121.126.161.117 attackspam
(sshd) Failed SSH login from 121.126.161.117 (-): 5 in the last 3600 secs
2019-11-14 17:18:13
175.120.105.73 attackbotsspam
UTC: 2019-11-13 port: 23/tcp
2019-11-14 17:09:40

Recently Reported IPs

18.138.222.198 18.138.23.239 18.138.41.41 18.138.240.51
18.138.3.93 18.138.215.12 18.138.24.145 18.138.31.99
18.138.45.70 18.138.49.237 18.138.87.174 18.138.53.110
18.138.67.226 18.138.53.160 18.138.86.63 18.138.56.128
18.138.77.127 18.138.90.119 18.139.104.66 18.139.111.118