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

Region: Oregon

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

;; QUESTION SECTION:
;44.245.2.221.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 11 18:25:40 CST 2025
;; MSG SIZE  rcvd: 105
Host info
221.2.245.44.in-addr.arpa domain name pointer ec2-44-245-2-221.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
221.2.245.44.in-addr.arpa	name = ec2-44-245-2-221.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
162.157.142.206 attack
Unauthorized connection attempt detected from IP address 162.157.142.206 to port 8000
2020-01-08 21:43:39
218.92.0.138 attackspambots
Jan  8 08:43:19 TORMINT sshd\[555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138  user=root
Jan  8 08:43:21 TORMINT sshd\[555\]: Failed password for root from 218.92.0.138 port 23501 ssh2
Jan  8 08:43:51 TORMINT sshd\[562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138  user=root
...
2020-01-08 21:51:16
54.37.205.162 attackspam
Jan  8 14:04:47 SilenceServices sshd[32214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.205.162
Jan  8 14:04:49 SilenceServices sshd[32214]: Failed password for invalid user ftp_user from 54.37.205.162 port 39332 ssh2
Jan  8 14:06:46 SilenceServices sshd[1388]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.205.162
2020-01-08 21:33:24
111.72.196.196 attack
2020-01-08 06:36:34 dovecot_login authenticator failed for (nxnno) [111.72.196.196]:49732 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=liyong@lerctr.org)
2020-01-08 07:05:55 dovecot_login authenticator failed for (fcjze) [111.72.196.196]:61233 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=liyong@lerctr.org)
2020-01-08 07:06:03 dovecot_login authenticator failed for (rspji) [111.72.196.196]:61233 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=liyong@lerctr.org)
...
2020-01-08 21:57:22
218.92.0.148 attack
k+ssh-bruteforce
2020-01-08 22:04:18
139.199.8.208 attackspam
Unauthorized access to SSH at 8/Jan/2020:13:06:02 +0000.
Received:  (SSH-2.0-libssh2_1.7.0)
2020-01-08 21:58:34
125.124.70.22 attackbotsspam
ssh failed login
2020-01-08 21:37:29
46.38.144.179 attack
Jan  8 14:27:24 relay postfix/smtpd\[18082\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 14:27:40 relay postfix/smtpd\[16970\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 14:28:09 relay postfix/smtpd\[18082\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 14:28:24 relay postfix/smtpd\[16970\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 14:28:52 relay postfix/smtpd\[23359\]: warning: unknown\[46.38.144.179\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-08 21:30:42
187.162.63.104 attackbotsspam
Automatic report - Port Scan Attack
2020-01-08 21:41:29
106.13.23.35 attackbots
Jan  8 13:06:50 IngegnereFirenze sshd[22978]: Failed password for invalid user zcx from 106.13.23.35 port 36352 ssh2
...
2020-01-08 21:32:04
167.71.57.65 attack
Jan  8 14:06:15 debian-2gb-nbg1-2 kernel: \[748090.254124\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=167.71.57.65 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=4989 PROTO=TCP SPT=48565 DPT=1723 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-08 21:47:44
134.209.102.147 attackspam
134.209.102.147 - - [08/Jan/2020:14:06:44 +0100] "POST /wp-login.php HTTP/1.1" 200 3121 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
134.209.102.147 - - [08/Jan/2020:14:06:45 +0100] "POST /wp-login.php HTTP/1.1" 200 3100 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-01-08 21:33:46
80.253.244.188 attackspam
Brute force SMTP login attempts.
2020-01-08 21:40:46
180.241.34.60 attackbots
Unauthorized connection attempt detected from IP address 180.241.34.60 to port 445
2020-01-08 22:03:08
180.250.248.169 attackbots
Jan  8 12:58:08 ip-172-31-62-245 sshd\[20485\]: Failed password for mail from 180.250.248.169 port 57156 ssh2\
Jan  8 13:01:53 ip-172-31-62-245 sshd\[20599\]: Invalid user jk from 180.250.248.169\
Jan  8 13:01:55 ip-172-31-62-245 sshd\[20599\]: Failed password for invalid user jk from 180.250.248.169 port 38200 ssh2\
Jan  8 13:05:47 ip-172-31-62-245 sshd\[20628\]: Invalid user miner from 180.250.248.169\
Jan  8 13:05:49 ip-172-31-62-245 sshd\[20628\]: Failed password for invalid user miner from 180.250.248.169 port 49198 ssh2\
2020-01-08 22:06:44

Recently Reported IPs

23.220.112.130 110.80.231.86 183.88.243.215 169.171.9.203
6.92.246.190 215.225.206.231 104.87.198.181 171.184.228.128
107.170.97.90 64.62.156.217 64.62.156.214 42.34.89.190
132.142.30.65 155.20.254.190 150.118.158.11 34.182.76.222
171.166.76.134 13.159.192.215 162.216.150.229 35.88.163.239