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: Kraków

Region: Malopolskie

Country: Poland

Internet Service Provider: NetWorkS!

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

;; QUESTION SECTION:
;2.57.149.200.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 13 21:11:06 CST 2024
;; MSG SIZE  rcvd: 105
Host info
Host 200.149.57.2.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 200.149.57.2.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.241.185.39 attack
FTP Brute Force
2019-12-08 21:51:01
218.78.29.16 attackspam
Dec  7 22:14:32 uapps sshd[4286]: Address 218.78.29.16 maps to 16.29.78.218.dial.xw.sh.dynamic.163data.com.cn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec  7 22:14:32 uapps sshd[4286]: User nobody from 218.78.29.16 not allowed because not listed in AllowUsers
Dec  7 22:14:32 uapps sshd[4286]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.78.29.16  user=nobody
Dec  7 22:14:34 uapps sshd[4286]: Failed password for invalid user nobody from 218.78.29.16 port 38382 ssh2
Dec  7 22:14:34 uapps sshd[4286]: Received disconnect from 218.78.29.16: 11: Bye Bye [preauth]
Dec  7 22:23:22 uapps sshd[4729]: Address 218.78.29.16 maps to 16.29.78.218.dial.xw.sh.dynamic.163data.com.cn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec  7 22:23:22 uapps sshd[4729]: User r.r from 218.78.29.16 not allowed because not listed in AllowUsers
Dec  7 22:23:22 uapps sshd[4729]: pam_unix(sshd:auth):........
-------------------------------
2019-12-08 21:56:12
37.59.37.69 attackbotsspam
Dec  8 09:00:43 ny01 sshd[7587]: Failed password for root from 37.59.37.69 port 41610 ssh2
Dec  8 09:07:20 ny01 sshd[8259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.37.69
Dec  8 09:07:21 ny01 sshd[8259]: Failed password for invalid user mysql from 37.59.37.69 port 45820 ssh2
2019-12-08 22:10:24
103.138.108.154 attack
firewall-block, port(s): 3390/tcp
2019-12-08 22:04:46
195.231.0.189 attackbots
Dec  7 22:13:03 vzhost sshd[19165]: reveeclipse mapping checking getaddrinfo for host189-0-231-195.serverdedicati.aruba.hostname [195.231.0.189] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec  7 22:13:03 vzhost sshd[19165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.231.0.189  user=r.r
Dec  7 22:13:05 vzhost sshd[19165]: Failed password for r.r from 195.231.0.189 port 49712 ssh2
Dec  7 22:13:06 vzhost sshd[19171]: reveeclipse mapping checking getaddrinfo for host189-0-231-195.serverdedicati.aruba.hostname [195.231.0.189] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec  7 22:13:06 vzhost sshd[19171]: Invalid user admin from 195.231.0.189
Dec  7 22:13:06 vzhost sshd[19171]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.231.0.189 
Dec  7 22:13:07 vzhost sshd[19171]: Failed password for invalid user admin from 195.231.0.189 port 52732 ssh2
Dec  7 22:13:08 vzhost sshd[19184]: reveeclipse mapping ........
-------------------------------
2019-12-08 22:29:55
185.205.46.116 attackbotsspam
Automatic report - XMLRPC Attack
2019-12-08 22:17:12
66.249.155.244 attackbotsspam
2019-12-08T13:41:40.189591shield sshd\[7167\]: Invalid user web from 66.249.155.244 port 38572
2019-12-08T13:41:40.192387shield sshd\[7167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.249.155.244
2019-12-08T13:41:42.036820shield sshd\[7167\]: Failed password for invalid user web from 66.249.155.244 port 38572 ssh2
2019-12-08T13:48:50.229584shield sshd\[9900\]: Invalid user agricola from 66.249.155.244 port 47822
2019-12-08T13:48:50.233728shield sshd\[9900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.249.155.244
2019-12-08 22:08:46
193.112.174.67 attack
Dec  8 12:36:32 MK-Soft-VM7 sshd[5318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.174.67 
Dec  8 12:36:34 MK-Soft-VM7 sshd[5318]: Failed password for invalid user dalheim from 193.112.174.67 port 43332 ssh2
...
2019-12-08 22:07:26
95.104.86.146 attackbots
UTC: 2019-12-07 port: 554/tcp
2019-12-08 22:21:04
54.36.241.186 attack
$f2bV_matches
2019-12-08 21:54:21
222.186.175.163 attackspam
Dec  8 13:47:12 marvibiene sshd[57250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163  user=root
Dec  8 13:47:14 marvibiene sshd[57250]: Failed password for root from 222.186.175.163 port 32334 ssh2
Dec  8 13:47:17 marvibiene sshd[57250]: Failed password for root from 222.186.175.163 port 32334 ssh2
Dec  8 13:47:12 marvibiene sshd[57250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163  user=root
Dec  8 13:47:14 marvibiene sshd[57250]: Failed password for root from 222.186.175.163 port 32334 ssh2
Dec  8 13:47:17 marvibiene sshd[57250]: Failed password for root from 222.186.175.163 port 32334 ssh2
...
2019-12-08 21:52:47
43.242.212.81 attackbotsspam
Dec  8 16:56:44 vtv3 sshd[30177]: Failed password for root from 43.242.212.81 port 36039 ssh2
Dec  8 17:02:54 vtv3 sshd[1087]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.242.212.81 
Dec  8 17:02:57 vtv3 sshd[1087]: Failed password for invalid user hovanes from 43.242.212.81 port 40782 ssh2
2019-12-08 22:06:50
211.192.167.36 attack
Dec  8 19:33:19 vibhu-HP-Z238-Microtower-Workstation sshd\[3161\]: Invalid user root@!QAZXSW@ from 211.192.167.36
Dec  8 19:33:19 vibhu-HP-Z238-Microtower-Workstation sshd\[3161\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.192.167.36
Dec  8 19:33:21 vibhu-HP-Z238-Microtower-Workstation sshd\[3161\]: Failed password for invalid user root@!QAZXSW@ from 211.192.167.36 port 60624 ssh2
Dec  8 19:40:14 vibhu-HP-Z238-Microtower-Workstation sshd\[3831\]: Invalid user ccccc from 211.192.167.36
Dec  8 19:40:14 vibhu-HP-Z238-Microtower-Workstation sshd\[3831\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.192.167.36
...
2019-12-08 22:14:43
128.199.145.205 attackbotsspam
Dec  8 09:40:51 cvbnet sshd[23083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.145.205 
Dec  8 09:40:53 cvbnet sshd[23083]: Failed password for invalid user radubarsan from 128.199.145.205 port 59125 ssh2
...
2019-12-08 22:24:02
132.145.218.241 attackspam
Dec  8 12:32:22 loxhost sshd\[14504\]: Invalid user kipping from 132.145.218.241 port 45480
Dec  8 12:32:22 loxhost sshd\[14504\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.145.218.241
Dec  8 12:32:24 loxhost sshd\[14504\]: Failed password for invalid user kipping from 132.145.218.241 port 45480 ssh2
Dec  8 12:38:27 loxhost sshd\[14764\]: Invalid user btsync from 132.145.218.241 port 57396
Dec  8 12:38:27 loxhost sshd\[14764\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.145.218.241
...
2019-12-08 22:08:00

Recently Reported IPs

239.181.149.194 119.64.185.158 23.109.170.232 192.178.50.66
193.42.96.70 167.172.77.245 192.252.212.28 69.4.234.70
23.225.121.228 120.245.60.16 185.222.58.241 110.180.18.38
45.196.214.80 222.13.230.221 146.190.72.131 77.91.68.175
193.187.128.211 87.70.41.55 103.116.164.17 120.245.60.252