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

Region: Central and Western District

Country: Hong Kong

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
52.229.169.70 attack
The IP has triggered Cloudflare WAF. CF-Ray: 541263a17a45dac8 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: HK | CF_IPClass: noRecord | Protocol: HTTP/2 | Method: GET | Host: api.skk.moe | User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1 | CF_DC: TPE. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 07:21:19
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.229.169.134
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15779
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.229.169.134.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Dec 25 21:45:40 CST 2021
;; MSG SIZE  rcvd: 107
Host info
Host 134.169.229.52.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.169.229.52.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.54.203.54 attack
Oct  3 02:57:52 staging sshd[184827]: Invalid user vss from 106.54.203.54 port 56344
Oct  3 02:57:52 staging sshd[184827]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.203.54 
Oct  3 02:57:52 staging sshd[184827]: Invalid user vss from 106.54.203.54 port 56344
Oct  3 02:57:54 staging sshd[184827]: Failed password for invalid user vss from 106.54.203.54 port 56344 ssh2
...
2020-10-03 14:59:06
222.186.31.166 attackspambots
2020-10-03T09:43:05.969228lavrinenko.info sshd[10055]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166  user=root
2020-10-03T09:43:07.852224lavrinenko.info sshd[10055]: Failed password for root from 222.186.31.166 port 64381 ssh2
2020-10-03T09:43:05.969228lavrinenko.info sshd[10055]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166  user=root
2020-10-03T09:43:07.852224lavrinenko.info sshd[10055]: Failed password for root from 222.186.31.166 port 64381 ssh2
2020-10-03T09:43:10.872519lavrinenko.info sshd[10055]: Failed password for root from 222.186.31.166 port 64381 ssh2
...
2020-10-03 14:55:20
114.33.252.118 attackspam
Port Scan detected!
...
2020-10-03 14:57:31
59.145.221.103 attackspam
Oct  3 07:53:51 buvik sshd[26048]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103
Oct  3 07:53:52 buvik sshd[26048]: Failed password for invalid user karol from 59.145.221.103 port 44545 ssh2
Oct  3 07:57:26 buvik sshd[26594]: Invalid user ubuntu from 59.145.221.103
...
2020-10-03 15:01:38
134.175.19.39 attackspam
Time:     Sat Oct  3 07:34:52 2020 +0200
IP:       134.175.19.39 (CN/China/-)
Failures: 5 (sshd)
Interval: 3600 seconds
Blocked:  Permanent Block [LF_SSHD]

Log entries:

Oct  3 07:18:40 mail-03 sshd[17286]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.19.39  user=root
Oct  3 07:18:41 mail-03 sshd[17286]: Failed password for root from 134.175.19.39 port 53078 ssh2
Oct  3 07:30:42 mail-03 sshd[17431]: Invalid user ubuntu from 134.175.19.39 port 55530
Oct  3 07:30:44 mail-03 sshd[17431]: Failed password for invalid user ubuntu from 134.175.19.39 port 55530 ssh2
Oct  3 07:34:47 mail-03 sshd[17502]: Invalid user sergey from 134.175.19.39 port 40026
2020-10-03 15:00:23
192.35.168.225 attackbotsspam
 TCP (SYN) 192.35.168.225:61075 -> port 9933, len 44
2020-10-03 14:40:54
202.152.1.89 attackbotsspam
Port scan: Attack repeated for 24 hours
2020-10-03 14:34:55
71.6.147.254 attackbots
 TCP (SYN) 71.6.147.254:26200 -> port 6789, len 44
2020-10-03 14:32:10
112.85.42.187 attackbots
Oct  3 09:08:05 ift sshd\[49200\]: Failed password for root from 112.85.42.187 port 34634 ssh2Oct  3 09:10:58 ift sshd\[49562\]: Failed password for root from 112.85.42.187 port 15789 ssh2Oct  3 09:11:00 ift sshd\[49562\]: Failed password for root from 112.85.42.187 port 15789 ssh2Oct  3 09:11:02 ift sshd\[49562\]: Failed password for root from 112.85.42.187 port 15789 ssh2Oct  3 09:15:23 ift sshd\[50336\]: Failed password for root from 112.85.42.187 port 12691 ssh2
...
2020-10-03 14:28:18
122.51.158.27 attackbotsspam
Oct  2 23:32:07 firewall sshd[7886]: Invalid user nick from 122.51.158.27
Oct  2 23:32:09 firewall sshd[7886]: Failed password for invalid user nick from 122.51.158.27 port 35440 ssh2
Oct  2 23:35:45 firewall sshd[7951]: Invalid user randy from 122.51.158.27
...
2020-10-03 14:36:36
79.135.73.141 attackbots
SSH login attempts.
2020-10-03 15:10:52
103.80.210.103 attack
445/tcp 445/tcp 445/tcp
[2020-08-17/10-02]3pkt
2020-10-03 14:52:57
123.31.26.144 attackbots
Invalid user gera from 123.31.26.144 port 20448
2020-10-03 15:00:36
106.12.87.149 attackbotsspam
$f2bV_matches
2020-10-03 14:35:15
186.47.213.34 attackbots
SSH login attempts.
2020-10-03 14:49:11

Recently Reported IPs

41.25.80.252 194.86.59.196 121.235.35.229 162.104.150.162
235.32.80.44 137.225.161.117 219.140.172.213 204.73.90.147
1.79.138.130 223.226.226.122 192.138.227.107 240.169.10.133
122.14.57.133 163.39.79.164 239.181.196.40 141.64.102.241
224.40.166.60 134.209.112.128 59.0.9.231 175.176.2.103