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

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

;; QUESTION SECTION:
;149.82.28.122.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 07:42:10 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 122.28.82.149.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 122.28.82.149.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
5.125.180.144 attack
Unauthorized connection attempt from IP address 5.125.180.144 on Port 445(SMB)
2020-03-11 01:44:26
223.206.155.121 attackspam
Automatic report - Port Scan
2020-03-11 01:36:43
193.31.117.22 attack
SpamScore above: 10.0
2020-03-11 01:35:26
202.131.156.5 attack
Port probing on unauthorized port 445
2020-03-11 01:56:27
49.145.239.68 attackspambots
Unauthorized connection attempt from IP address 49.145.239.68 on Port 445(SMB)
2020-03-11 01:38:36
36.80.11.114 attack
Unauthorized connection attempt from IP address 36.80.11.114 on Port 445(SMB)
2020-03-11 01:51:51
148.233.136.34 attack
Invalid user ftpuser from 148.233.136.34 port 48400
2020-03-11 01:30:20
222.186.169.194 attackbots
Mar 10 07:29:20 auw2 sshd\[4634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Mar 10 07:29:22 auw2 sshd\[4634\]: Failed password for root from 222.186.169.194 port 48728 ssh2
Mar 10 07:29:39 auw2 sshd\[4644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Mar 10 07:29:41 auw2 sshd\[4644\]: Failed password for root from 222.186.169.194 port 41838 ssh2
Mar 10 07:29:44 auw2 sshd\[4644\]: Failed password for root from 222.186.169.194 port 41838 ssh2
2020-03-11 01:45:09
5.135.165.55 attackbotsspam
SSH login attempts.
2020-03-11 01:40:48
222.186.175.169 attackspam
Mar 10 18:09:20 sso sshd[15969]: Failed password for root from 222.186.175.169 port 35224 ssh2
Mar 10 18:09:23 sso sshd[15969]: Failed password for root from 222.186.175.169 port 35224 ssh2
...
2020-03-11 01:15:02
116.107.51.202 attackspam
1583831860 - 03/10/2020 10:17:40 Host: 116.107.51.202/116.107.51.202 Port: 445 TCP Blocked
2020-03-11 01:27:51
49.151.245.48 attackbotsspam
Honeypot attack, port: 445, PTR: dsl.49.151.245.48.pldt.net.
2020-03-11 01:42:45
125.27.179.174 attack
(sshd) Failed SSH login from 125.27.179.174 (TH/Thailand/node-zhq.pool-125-27.dynamic.totinternet.net): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Mar 10 05:17:34 host sshd[99090]: Did not receive identification string from 125.27.179.174 port 56537
2020-03-11 01:28:18
217.64.22.34 attackbotsspam
20/3/10@05:17:24: FAIL: Alarm-Network address from=217.64.22.34
20/3/10@05:17:24: FAIL: Alarm-Network address from=217.64.22.34
...
2020-03-11 01:34:55
185.175.93.14 attack
Fail2Ban Ban Triggered
2020-03-11 01:51:23

Recently Reported IPs

220.218.223.127 248.187.98.152 252.210.112.73 30.36.254.13
64.134.47.126 28.129.139.119 175.3.38.0 236.185.26.202
132.21.220.36 171.176.128.251 93.27.149.0 63.135.231.143
30.30.195.71 240.142.148.90 168.57.98.235 251.231.207.156
144.241.194.8 115.123.61.36 62.94.132.66 41.205.113.97