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

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
106.122.169.173 attack
Unauthorized connection attempt detected from IP address 106.122.169.173 to port 6656 [T]
2020-01-30 17:04:39
106.122.169.32 attackbots
Unauthorized connection attempt detected from IP address 106.122.169.32 to port 6656 [T]
2020-01-27 07:30:38
106.122.169.247 attackbotsspam
Unauthorized connection attempt detected from IP address 106.122.169.247 to port 6656 [T]
2020-01-27 04:34:36
106.122.169.156 attackbotsspam
The IP has triggered Cloudflare WAF. CF-Ray: 54174bd45836eef2 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/2 | Method: GET | Host: api.skk.moe | User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Safari/605.1.15 | CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 00:24:29
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.122.169.124
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62981
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;106.122.169.124.		IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 14:28:18 CST 2022
;; MSG SIZE  rcvd: 108
Host info
124.169.122.106.in-addr.arpa domain name pointer 124.169.122.106.broad.xm.fj.dynamic.163data.com.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
124.169.122.106.in-addr.arpa	name = 124.169.122.106.broad.xm.fj.dynamic.163data.com.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
62.231.7.221 attack
2020-01-29T04:03:01.243Z CLOSE host=62.231.7.221 port=51036 fd=4 time=20.008 bytes=15
...
2020-03-13 02:26:56
69.70.145.170 attackbots
Invalid user siteadmin from 69.70.145.170 port 16137
2020-03-13 02:06:14
146.185.203.177 attackbotsspam
B: zzZZzz blocked content access
2020-03-13 02:19:44
5.135.101.228 attackbotsspam
Mar 12 19:06:30 vpn01 sshd[15653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.135.101.228
Mar 12 19:06:32 vpn01 sshd[15653]: Failed password for invalid user lichaonan from 5.135.101.228 port 48288 ssh2
...
2020-03-13 02:08:21
73.202.137.196 attackbots
2019-10-24T09:40:48.815Z CLOSE host=73.202.137.196 port=56090 fd=4 time=30.012 bytes=33
...
2020-03-13 02:02:22
34.80.30.202 attackspambots
Lines containing failures of 34.80.30.202
Mar 12 06:27:13 kmh-vmh-001-fsn05 sshd[14164]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.80.30.202  user=r.r
Mar 12 06:27:15 kmh-vmh-001-fsn05 sshd[14164]: Failed password for r.r from 34.80.30.202 port 51390 ssh2
Mar 12 06:27:16 kmh-vmh-001-fsn05 sshd[14164]: Received disconnect from 34.80.30.202 port 51390:11: Bye Bye [preauth]
Mar 12 06:27:16 kmh-vmh-001-fsn05 sshd[14164]: Disconnected from authenticating user r.r 34.80.30.202 port 51390 [preauth]
Mar 12 06:40:15 kmh-vmh-001-fsn05 sshd[16377]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.80.30.202  user=r.r
Mar 12 06:40:16 kmh-vmh-001-fsn05 sshd[16377]: Failed password for r.r from 34.80.30.202 port 50118 ssh2
Mar 12 06:40:17 kmh-vmh-001-fsn05 sshd[16377]: Received disconnect from 34.80.30.202 port 50118:11: Bye Bye [preauth]
Mar 12 06:40:17 kmh-vmh-001-fsn05 sshd[16377]: Disconnecte........
------------------------------
2020-03-13 02:33:36
65.49.20.69 attackbots
2020-03-04T03:50:45.974Z CLOSE host=65.49.20.69 port=40338 fd=5 time=20.002 bytes=18
...
2020-03-13 02:14:25
68.194.22.92 attackspambots
2020-03-05T06:54:40.854Z CLOSE host=68.194.22.92 port=34648 fd=4 time=60.040 bytes=103
...
2020-03-13 02:07:33
77.40.58.102 attack
suspicious action Thu, 12 Mar 2020 09:29:22 -0300
2020-03-13 02:20:46
61.94.143.232 attackbots
2019-11-05T14:12:39.993Z CLOSE host=61.94.143.232 port=49286 fd=4 time=20.008 bytes=4
...
2020-03-13 02:29:45
77.109.112.83 attack
2020-02-01T09:55:13.418Z CLOSE host=77.109.112.83 port=58338 fd=4 time=20.013 bytes=5
2020-02-01T09:55:13.418Z CLOSE host=77.109.112.83 port=58340 fd=5 time=20.006 bytes=28
...
2020-03-13 01:56:55
65.49.20.68 attack
2020-03-08T00:57:43.614Z CLOSE host=65.49.20.68 port=65106 fd=4 time=20.016 bytes=21
...
2020-03-13 02:14:52
64.52.173.98 attackbotsspam
2020-01-13T04:27:29.130Z CLOSE host=64.52.173.98 port=58856 fd=4 time=20.020 bytes=30
...
2020-03-13 02:17:58
61.77.146.126 attackbots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-03-13 02:05:38
73.70.218.63 attackbots
2020-01-18T08:07:27.606Z CLOSE host=73.70.218.63 port=54978 fd=4 time=20.010 bytes=12
...
2020-03-13 02:00:35

Recently Reported IPs

106.122.169.120 106.122.169.114 106.122.169.101 106.122.169.0
106.122.169.112 106.122.169.12 106.122.169.110 106.122.169.116
106.122.169.108 106.122.169.119 106.122.169.131 106.122.169.132
106.122.169.122 106.122.169.134 106.122.169.14 106.122.169.140
106.122.169.126 106.122.169.136 106.122.169.139 106.122.169.146