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

;; QUESTION SECTION:
;106.122.169.149.		IN	A

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

;; Query time: 74 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 14:28:22 CST 2022
;; MSG SIZE  rcvd: 108
Host info
149.169.122.106.in-addr.arpa domain name pointer 149.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:
149.169.122.106.in-addr.arpa	name = 149.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
49.67.67.106 attackbotsspam
2019-06-23T21:33:09.282661 X postfix/smtpd[39209]: warning: unknown[49.67.67.106]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-06-23T21:34:17.495876 X postfix/smtpd[39209]: warning: unknown[49.67.67.106]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-06-23T21:51:52.107894 X postfix/smtpd[41518]: warning: unknown[49.67.67.106]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-06-24 10:49:28
91.61.37.190 attackbotsspam
20 attempts against mh-ssh on hill.magehost.pro
2019-06-24 11:15:46
193.56.28.203 attack
2019-06-17 01:49:42 dovecot_login authenticator failed for (sABSga5V) [193.56.28.203]:54443: 535 Incorrect authentication data (set_id=arnis)
2019-06-17 01:49:48 dovecot_login authenticator failed for (twVIohFh) [193.56.28.203]:54981: 535 Incorrect authentication data (set_id=arnis)
2019-06-17 01:49:58 dovecot_login authenticator failed for (0vKUoxgxp) [193.56.28.203]:56143: 535 Incorrect authentication data (set_id=arnis)
2019-06-17 01:50:13 dovecot_login authenticator failed for (Wjgda8) [193.56.28.203]:60289: 535 Incorrect authentication data (set_id=arnis)
2019-06-17 01:50:15 dovecot_login authenticator failed for (KmiL2ek) [193.56.28.203]:58019: 535 Incorrect authentication data
2019-06-17 01:50:30 dovecot_login authenticator failed for (YC4tuc) [193.56.28.203]:60586: 535 Incorrect authentication data
2019-06-17 01:50:38 dovecot_login authenticator failed for (4jJBkY64XO) [193.56.28.203]:61952: 535 Incorrect authentication data
2019-06-17 01:50:51 dovecot_login auth........
------------------------------
2019-06-24 11:21:46
94.177.203.136 attack
2019-06-24T01:13:09.298949stark.klein-stark.info sshd\[5316\]: Invalid user adminuser from 94.177.203.136 port 33514
2019-06-24T01:13:09.305608stark.klein-stark.info sshd\[5316\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.203.136
2019-06-24T01:13:11.279230stark.klein-stark.info sshd\[5316\]: Failed password for invalid user adminuser from 94.177.203.136 port 33514 ssh2
...
2019-06-24 10:59:02
168.228.151.119 attackspambots
SMTP-sasl brute force
...
2019-06-24 10:47:54
178.128.171.212 attackspambots
fail2ban honeypot
2019-06-24 11:17:20
104.248.179.98 attack
www.handydirektreparatur.de 104.248.179.98 \[24/Jun/2019:02:45:45 +0200\] "POST /wp-login.php HTTP/1.1" 200 5667 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
www.handydirektreparatur.de 104.248.179.98 \[24/Jun/2019:02:45:46 +0200\] "POST /xmlrpc.php HTTP/1.1" 200 4116 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-06-24 11:33:38
200.76.226.243 attackspambots
Jun 24 02:30:13 mail sshd\[5138\]: Invalid user ilog from 200.76.226.243
Jun 24 02:30:13 mail sshd\[5138\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.76.226.243
Jun 24 02:30:15 mail sshd\[5138\]: Failed password for invalid user ilog from 200.76.226.243 port 48214 ssh2
Jun 24 02:32:27 mail sshd\[5231\]: Invalid user divya from 200.76.226.243
Jun 24 02:32:27 mail sshd\[5231\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.76.226.243
2019-06-24 11:09:22
212.237.50.189 attackspam
5901/tcp 5901/tcp 5901/tcp...
[2019-04-23/06-22]6pkt,1pt.(tcp)
2019-06-24 10:54:24
173.167.200.227 attackspambots
Jan 29 12:56:03 microserver sshd[38165]: Invalid user teste from 173.167.200.227 port 24595
Jan 29 12:56:03 microserver sshd[38165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.167.200.227
Jan 29 12:56:05 microserver sshd[38165]: Failed password for invalid user teste from 173.167.200.227 port 24595 ssh2
Jan 29 13:00:29 microserver sshd[38638]: Invalid user jira from 173.167.200.227 port 30831
Jan 29 13:00:29 microserver sshd[38638]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.167.200.227
Feb  1 07:10:19 microserver sshd[33357]: Invalid user zbomc from 173.167.200.227 port 39757
Feb  1 07:10:19 microserver sshd[33357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.167.200.227
Feb  1 07:10:21 microserver sshd[33357]: Failed password for invalid user zbomc from 173.167.200.227 port 39757 ssh2
Feb  1 07:14:38 microserver sshd[33421]: pam_unix(sshd:auth): authentication fai
2019-06-24 10:58:18
178.33.110.200 attackbots
wordpress exploit scan
...
2019-06-24 10:55:30
128.199.133.249 attackbots
Jun 24 04:46:05 vpn01 sshd\[30447\]: Invalid user sa from 128.199.133.249
Jun 24 04:46:05 vpn01 sshd\[30447\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.133.249
Jun 24 04:46:07 vpn01 sshd\[30447\]: Failed password for invalid user sa from 128.199.133.249 port 51741 ssh2
2019-06-24 11:23:54
139.162.112.248 attackbots
3389BruteforceFW21
2019-06-24 11:25:33
201.231.58.42 attack
Brute force attempt
2019-06-24 11:00:21
54.39.15.178 attackspambots
ADMIN
2019-06-24 10:52:44

Recently Reported IPs

106.122.169.162 106.122.169.164 106.122.169.168 106.122.169.167
106.122.169.17 106.122.169.170 106.122.169.172 106.122.169.180
106.122.169.178 106.122.169.18 106.122.169.187 106.122.169.182
106.122.169.188 106.122.169.193 106.122.169.191 106.122.169.194
106.122.169.199 106.122.169.20 106.122.169.196 106.122.169.200