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

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

;; QUESTION SECTION:
;54.232.214.129.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 21:46:09 CST 2025
;; MSG SIZE  rcvd: 107
Host info
129.214.232.54.in-addr.arpa domain name pointer ec2-54-232-214-129.sa-east-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
129.214.232.54.in-addr.arpa	name = ec2-54-232-214-129.sa-east-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
188.190.70.110 attackbots
scan z
2019-12-02 01:48:25
110.11.227.225 attack
Port 1433 Scan
2019-12-02 02:01:52
177.85.3.69 attackbots
Fail2Ban Ban Triggered
2019-12-02 01:51:21
143.0.25.24 attackspam
Unauthorised access (Dec  1) SRC=143.0.25.24 LEN=44 TTL=47 ID=758 TCP DPT=23 WINDOW=23361 SYN
2019-12-02 01:41:13
222.186.175.215 attack
Dec  1 12:22:50 TORMINT sshd\[26014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.215  user=root
Dec  1 12:22:52 TORMINT sshd\[26014\]: Failed password for root from 222.186.175.215 port 43072 ssh2
Dec  1 12:23:09 TORMINT sshd\[26021\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.215  user=root
...
2019-12-02 01:26:37
176.31.116.57 attackspambots
[ssh] SSH attack
2019-12-02 01:58:48
45.82.153.80 attack
2019-12-01 18:47:42 dovecot_login authenticator failed for \(\[45.82.153.80\]\) \[45.82.153.80\]: 535 Incorrect authentication data \(set_id=ms@opso.it\)
2019-12-01 18:47:54 dovecot_login authenticator failed for \(\[45.82.153.80\]\) \[45.82.153.80\]: 535 Incorrect authentication data
2019-12-01 18:48:05 dovecot_login authenticator failed for \(\[45.82.153.80\]\) \[45.82.153.80\]: 535 Incorrect authentication data
2019-12-01 18:48:23 dovecot_login authenticator failed for \(\[45.82.153.80\]\) \[45.82.153.80\]: 535 Incorrect authentication data
2019-12-01 18:48:30 dovecot_login authenticator failed for \(\[45.82.153.80\]\) \[45.82.153.80\]: 535 Incorrect authentication data
2019-12-02 01:55:55
209.85.220.69 attackbots
Sending out some get laid now type spam emails
from IP 209.85.220.69  (Google.com) 

The spammer's websites are located at 

https://docs.google.com/forms/d/e/1FAIpQLSeJ6xrSPrAFWOMMXgCExIRlu7zB3VNCzARdwdlR5uedryWSvg/viewform?vc=0&c=0&w=1&usp=mail_form_link
IP: 172.217.14.206 (Google.com) 

http://meetsafes.us/meet.php
IP: 198.54.120.157 
(namecheap.com / namecheaphosting.com) 

Which redirects to 
http://getlaidsecrets.com/presales/RF_Dating_Prelanders/lp5/?aff_id=3855&aff_sub=&aff_sub2=b7c916662fd3310772724b17de49cf9f355a1344&aff_sub3=&aff_sub4=&aff_sub5=&aff_unique5=kvSq120159927&trn=102cc1db6c7aae3b42a2606c020aff
IP: 107.170.239.229 (digitalocean.com)


Which redirects to 
http://fastsecuredating.com/?page=land2/512_ac_ffriend&long=y&x_source=vip52744.46200-1973716.GSL-3855.102d7abb8fba79005993e4cf832a3e..Web.&eml=
IP: 35.174.201.165, 34.238.141.146
(amazon.com / amazonaws.com)

DO NOT go to any of these sites or buy
anything from any of these sites as it is a scam!
2019-12-02 01:54:12
134.175.49.215 attackbots
SSH bruteforce
2019-12-02 01:51:46
112.85.42.180 attackspam
Dec  1 14:28:27 wh01 sshd[32001]: Failed password for root from 112.85.42.180 port 40999 ssh2
Dec  1 14:28:28 wh01 sshd[32001]: Failed password for root from 112.85.42.180 port 40999 ssh2
Dec  1 14:28:29 wh01 sshd[32001]: Failed password for root from 112.85.42.180 port 40999 ssh2
Dec  1 18:21:16 wh01 sshd[17580]: Failed password for root from 112.85.42.180 port 26209 ssh2
Dec  1 18:21:17 wh01 sshd[17580]: Failed password for root from 112.85.42.180 port 26209 ssh2
Dec  1 18:21:18 wh01 sshd[17580]: Failed password for root from 112.85.42.180 port 26209 ssh2
2019-12-02 01:23:49
192.42.116.16 attackspambots
fail2ban
2019-12-02 01:19:04
123.22.59.103 attack
Dec  1 15:42:06 vpn01 sshd[4909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.22.59.103
Dec  1 15:42:08 vpn01 sshd[4909]: Failed password for invalid user admin from 123.22.59.103 port 51176 ssh2
...
2019-12-02 01:48:54
146.0.209.72 attack
5x Failed Password
2019-12-02 01:39:35
42.85.146.45 attackspam
" "
2019-12-02 01:34:55
94.232.173.95 attack
Dec  1 15:27:09 mail1 sshd\[30529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.232.173.95  user=smmsp
Dec  1 15:27:12 mail1 sshd\[30529\]: Failed password for smmsp from 94.232.173.95 port 33896 ssh2
Dec  1 15:38:40 mail1 sshd\[3570\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.232.173.95  user=root
Dec  1 15:38:41 mail1 sshd\[3570\]: Failed password for root from 94.232.173.95 port 47900 ssh2
Dec  1 15:42:08 mail1 sshd\[5327\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.232.173.95  user=root
...
2019-12-02 01:48:08

Recently Reported IPs

61.150.38.11 51.145.252.28 132.11.215.179 76.215.173.218
255.129.42.231 234.241.5.18 191.210.35.204 64.31.125.40
44.210.147.195 147.201.150.9 234.112.158.122 201.33.26.190
84.136.66.255 4.179.61.226 101.20.58.124 63.33.204.174
41.54.52.68 76.225.184.122 192.95.97.235 144.108.93.143