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:
IP Type Details Datetime
54.213.133.161 attackspam
02/08/2020-06:55:46.580498 54.213.133.161 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-08 17:41:52
54.213.133.161 attackspambots
02/07/2020-01:20:57.787455 54.213.133.161 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-07 08:36:19
54.213.133.161 attack
02/06/2020-07:15:46.291483 54.213.133.161 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-06 14:57:46
54.213.133.161 attackspambots
02/05/2020-15:52:31.946221 54.213.133.161 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-05 23:06:33
54.213.116.198 attack
01/09/2020-00:16:51.028263 54.213.116.198 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-09 07:30:14
54.213.116.198 attackbotsspam
01/08/2020-09:48:35.475218 54.213.116.198 Protocol: 6 SURICATA TLS invalid record/traffic
2020-01-08 16:53:21
54.213.116.173 attack
Bad bot/spoofed identity
2019-10-02 18:17:19
54.213.182.74 attack
Sending out Netflix spam from IP 54.240.14.174 
(amazon.com / amazonaws.com) 

I have NEVER been a Netflix customer and
never asked for this junk. 

The website spammed out is 

https://www.netflix.com/signup/creditoption?nftoken=BQAbAAEBEA77T6CHfer3tv8qolkSAduAkLFC%2FFYUyiUS4Sdi62TDOAptLP7WiMxUQK74rIuN%2BRXrWDnwU8vxCNSC2khWG0ZmflN2tsqMsqNHMDWRdKmlf6XFVqwlgd%2BFLY2Nz88IH4y3pcuOeFYD5X9L4G9ZZfbRHvrmZF%2FjsAyUI1f5mpTFg3eEFWfNQayYDiVrbb%2FU65EF%2B0XXrVI0T4jKa2zmCB8w5g%3D%3D&lnktrk=EMP&g=AEF2F71097E503EBEB44921E2720235C64526E40&lkid=URL_SIGNUP_CREDIT
IPs: 54.69.16.110, 54.70.73.70, 54.149.101.155,
54.201.91.38, 54.213.182.74, 52.37.77.112,
52.41.20.47, 52.41.193.16
(amazon.com / amazonaws.com) 

amazon are pure scumbags who allow their 
customers to send out spam and do nothing 
about it! 
Report via email and website at 
https://support.aws.amazon.com/#/contacts/report-abuse
2019-09-26 18:05:05
54.213.154.238 attackspambots
This IP address was blacklisted for the following reason:  /nl/jobs/it-tester-mv-arnhem/ @ 2019-09-05T08:29:26+02:00.
2019-09-09 08:13:37
54.213.141.112 attackbots
Brute forcing Wordpress login
2019-08-13 14:31:32
54.213.159.205 attack
Lines containing failures of 54.213.159.205
auth.log:Aug  9 01:07:05 omfg sshd[9529]: Connection from 54.213.159.205 port 36718 on 78.46.60.40 port 22
auth.log:Aug  9 01:07:26 omfg sshd[9529]: Connection closed by 54.213.159.205 port 36718 [preauth]
auth.log:Aug  9 01:07:26 omfg sshd[9537]: Connection from 54.213.159.205 port 34402 on 78.46.60.40 port 22
auth.log:Aug  9 01:07:41 omfg sshd[9537]: fatal: Unable to negotiate whostnameh 54.213.159.205 port 34402: no matching host key type found. Their offer: ecdsa-sha2-nistp384 [preauth]
auth.log:Aug  9 01:07:48 omfg sshd[9611]: Connection from 54.213.159.205 port 45866 on 78.46.60.40 port 22
auth.log:Aug  9 01:07:56 omfg sshd[9611]: fatal: Unable to negotiate whostnameh 54.213.159.205 port 45866: no matching host key type found. Their offer: ecdsa-sha2-nistp521 [preauth]
auth.log:Aug  9 01:08:03 omfg sshd[9684]: Connection from 54.213.159.205 port 54380 on 78.46.60.40 port 22
auth.log:Aug  9 01:08:11 omfg sshd[9684]: Connec........
------------------------------
2019-08-09 20:00:23
54.213.173.233 attackspambots
Jul 22 17:29:43 MK-Soft-VM4 sshd\[11636\]: Invalid user anand from 54.213.173.233 port 49194
Jul 22 17:29:43 MK-Soft-VM4 sshd\[11636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.213.173.233
Jul 22 17:29:45 MK-Soft-VM4 sshd\[11636\]: Failed password for invalid user anand from 54.213.173.233 port 49194 ssh2
...
2019-07-23 02:33:40
54.213.173.233 attackbots
Jul 22 07:19:14 debian sshd\[29106\]: Invalid user db2inst1 from 54.213.173.233 port 40494
Jul 22 07:19:14 debian sshd\[29106\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.213.173.233
...
2019-07-22 14:26:48
54.213.173.233 attack
Jul 21 20:25:46 debian sshd\[17562\]: Invalid user lu from 54.213.173.233 port 50698
Jul 21 20:25:46 debian sshd\[17562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.213.173.233
...
2019-07-22 03:26:57
Whois info:
b
Dig info:
b'
; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> 54.213.1.67
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56858
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;54.213.1.67.			IN	A

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Jun 30 16:35:41 CST 2021
;; MSG SIZE  rcvd: 40

'
Host info
67.1.213.54.in-addr.arpa domain name pointer ec2-54-213-1-67.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
67.1.213.54.in-addr.arpa	name = ec2-54-213-1-67.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
182.61.176.53 attack
Nov 27 09:38:14 mail sshd[28172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.176.53 
Nov 27 09:38:16 mail sshd[28172]: Failed password for invalid user mckibbon from 182.61.176.53 port 48746 ssh2
Nov 27 09:45:17 mail sshd[31467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.176.53
2019-11-27 19:15:07
209.141.48.68 attackbots
Nov 27 08:29:43 MK-Soft-Root2 sshd[5673]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.48.68 
Nov 27 08:29:46 MK-Soft-Root2 sshd[5673]: Failed password for invalid user mukund from 209.141.48.68 port 40850 ssh2
...
2019-11-27 19:15:19
223.71.167.155 attack
[portscan] udp/500 [isakmp]
*(RWIN=-)(11271302)
2019-11-27 19:19:07
109.70.100.20 attack
Unauthorized access detected from banned ip
2019-11-27 19:35:53
122.152.216.42 attack
Nov 27 11:43:09 vps647732 sshd[26886]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.152.216.42
Nov 27 11:43:12 vps647732 sshd[26886]: Failed password for invalid user ogrady from 122.152.216.42 port 55858 ssh2
...
2019-11-27 19:29:39
43.255.140.218 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-27 19:50:25
206.189.230.98 attackbotsspam
206.189.230.98 - - \[27/Nov/2019:07:23:52 +0100\] "POST /wp-login.php HTTP/1.0" 200 6581 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
206.189.230.98 - - \[27/Nov/2019:07:23:54 +0100\] "POST /wp-login.php HTTP/1.0" 200 6394 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
206.189.230.98 - - \[27/Nov/2019:07:23:59 +0100\] "POST /wp-login.php HTTP/1.0" 200 6392 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-27 19:28:44
217.128.192.117 attackspambots
serveres are UTC -0500
Lines containing failures of 217.128.192.117
Nov 27 02:50:13 tux2 sshd[20911]: Failed password for news from 217.128.192.117 port 42985 ssh2
Nov 27 02:50:13 tux2 sshd[20911]: Received disconnect from 217.128.192.117 port 42985:11: Bye Bye [preauth]
Nov 27 02:50:13 tux2 sshd[20911]: Disconnected from authenticating user news 217.128.192.117 port 42985 [preauth]
Nov 27 02:56:08 tux2 sshd[21227]: Invalid user cath from 217.128.192.117 port 33334
Nov 27 02:56:08 tux2 sshd[21227]: Failed password for invalid user cath from 217.128.192.117 port 33334 ssh2
Nov 27 02:56:08 tux2 sshd[21227]: Received disconnect from 217.128.192.117 port 33334:11: Bye Bye [preauth]
Nov 27 02:56:08 tux2 sshd[21227]: Disconnected from invalid user cath 217.128.192.117 port 33334 [preauth]
Nov 27 02:59:29 tux2 sshd[21411]: Invalid user lisa from 217.128.192.117 port 32696
Nov 27 02:59:29 tux2 sshd[21411]: Failed password for invalid user lisa from 217.128.192.117 port 32696 ssh........
------------------------------
2019-11-27 19:22:37
185.143.223.148 attack
ET DROP Dshield Block Listed Source group 1 - port: 322 proto: TCP cat: Misc Attack
2019-11-27 19:06:13
157.245.111.175 attackbotsspam
Nov 27 11:09:56 vserver sshd\[5821\]: Invalid user tracee from 157.245.111.175Nov 27 11:09:58 vserver sshd\[5821\]: Failed password for invalid user tracee from 157.245.111.175 port 58840 ssh2Nov 27 11:13:44 vserver sshd\[5843\]: Invalid user server from 157.245.111.175Nov 27 11:13:46 vserver sshd\[5843\]: Failed password for invalid user server from 157.245.111.175 port 38390 ssh2
...
2019-11-27 19:39:56
217.160.109.72 attack
2019-11-27T11:24:20.510666abusebot.cloudsearch.cf sshd\[5364\]: Invalid user trombone from 217.160.109.72 port 36413
2019-11-27 19:33:06
221.162.255.78 attack
Nov 27 10:40:20 XXX sshd[11517]: Invalid user ofsaa from 221.162.255.78 port 36076
2019-11-27 19:30:54
128.199.142.138 attack
Nov 27 11:35:30 v22019058497090703 sshd[10134]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138
Nov 27 11:35:32 v22019058497090703 sshd[10134]: Failed password for invalid user rename from 128.199.142.138 port 39050 ssh2
Nov 27 11:40:36 v22019058497090703 sshd[10712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138
...
2019-11-27 19:31:46
125.64.94.211 attackbots
27.11.2019 08:49:11 Connection to port 9200 blocked by firewall
2019-11-27 19:23:03
180.183.177.147 attack
Honeypot attack, port: 445, PTR: mx-ll-180.183.177-147.dynamic.3bb.co.th.
2019-11-27 19:42:40

Recently Reported IPs

54.251.174.71 37.71.66.126 116.179.32.198 54.254.89.31
116.179.32.197 54.169.162.102 54.255.22.173 18.138.180.52
13.88.221.138 116.179.32.214 116.179.32.112 106.197.75.129
106.197.75.137 85.215.233.180 201.175.211.95 23.148.208.16
154.16.65.112 220.181.108.180 223.88.18.185 173.233.87.5