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

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
49.49.146.110 attackspam
Unauthorized connection attempt detected from IP address 49.49.146.110 to port 445
2020-04-16 12:52:03
49.49.141.60 attack
Nov 30 10:30:47 sanyalnet-cloud-vps2 sshd[2185]: Connection from 49.49.141.60 port 45524 on 45.62.253.138 port 22
Nov 30 10:30:53 sanyalnet-cloud-vps2 sshd[2185]: reveeclipse mapping checking getaddrinfo for mx-ll-49.49.141-60.dynamic.3bb.co.th [49.49.141.60] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 30 10:30:53 sanyalnet-cloud-vps2 sshd[2185]: Invalid user admin from 49.49.141.60 port 45524
Nov 30 10:30:53 sanyalnet-cloud-vps2 sshd[2185]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.49.141.60
Nov 30 10:30:54 sanyalnet-cloud-vps2 sshd[2185]: Failed password for invalid user admin from 49.49.141.60 port 45524 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.49.141.60
2019-11-30 19:49:39
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.49.14.44
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13519
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.49.14.44.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 24 15:25:39 CST 2023
;; MSG SIZE  rcvd: 104
Host info
44.14.49.49.in-addr.arpa domain name pointer mx-ll-49.49.14-44.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.14.49.49.in-addr.arpa	name = mx-ll-49.49.14-44.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
66.49.84.65 attackbots
Jan 14 18:12:19 vpn sshd[9088]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.49.84.65
Jan 14 18:12:21 vpn sshd[9088]: Failed password for invalid user admin from 66.49.84.65 port 41946 ssh2
Jan 14 18:15:22 vpn sshd[9096]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.49.84.65
2020-01-05 18:08:17
66.70.177.156 attack
Jan 15 23:03:02 vpn sshd[14816]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.177.156
Jan 15 23:03:04 vpn sshd[14816]: Failed password for invalid user qbtuser from 66.70.177.156 port 33894 ssh2
Jan 15 23:05:56 vpn sshd[14827]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.177.156
2020-01-05 18:03:40
67.41.195.160 attackspambots
Jan  2 05:35:12 vpn sshd[17072]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.41.195.160
Jan  2 05:35:14 vpn sshd[17072]: Failed password for invalid user guest from 67.41.195.160 port 35886 ssh2
Jan  2 05:38:44 vpn sshd[17093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.41.195.160
2020-01-05 17:39:07
62.150.134.233 attackbots
Unauthorized connection attempt detected from IP address 62.150.134.233 to port 2220 [J]
2020-01-05 17:57:48
66.70.176.199 attack
Nov 28 15:43:56 vpn sshd[17105]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.176.199
Nov 28 15:43:58 vpn sshd[17105]: Failed password for invalid user apache from 66.70.176.199 port 34500 ssh2
Nov 28 15:46:33 vpn sshd[17118]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.176.199
2020-01-05 18:04:22
66.68.133.120 attackbots
Dec 23 21:26:44 vpn sshd[20047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.68.133.120
Dec 23 21:26:45 vpn sshd[20047]: Failed password for invalid user deploy from 66.68.133.120 port 32882 ssh2
Dec 23 21:30:59 vpn sshd[20060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.68.133.120
2020-01-05 18:07:12
107.147.138.127 attack
*Port Scan* detected from 107.147.138.127 (US/United States/-). 4 hits in the last 115 seconds
2020-01-05 17:47:33
176.113.115.50 attack
Jan  5 10:30:14 debian-2gb-nbg1-2 kernel: \[475936.740705\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=176.113.115.50 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=24830 PROTO=TCP SPT=54667 DPT=7555 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-05 17:47:02
78.47.50.237 attackbots
Unauthorized connection attempt detected from IP address 78.47.50.237 to port 2220 [J]
2020-01-05 18:14:41
67.188.137.57 attackspam
Jan 14 12:10:55 vpn sshd[7562]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.188.137.57
Jan 14 12:10:57 vpn sshd[7562]: Failed password for invalid user cmd from 67.188.137.57 port 51888 ssh2
Jan 14 12:14:16 vpn sshd[7571]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.188.137.57
2020-01-05 17:53:07
66.70.130.154 attack
Mar  3 11:01:44 vpn sshd[25115]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.70.130.154
Mar  3 11:01:46 vpn sshd[25115]: Failed password for invalid user ez from 66.70.130.154 port 35300 ssh2
Mar  3 11:07:41 vpn sshd[25128]: Failed password for root from 66.70.130.154 port 38602 ssh2
2020-01-05 18:05:43
66.75.237.105 attackspambots
Feb 25 22:08:04 vpn sshd[21470]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.75.237.105
Feb 25 22:08:07 vpn sshd[21470]: Failed password for invalid user ftptest from 66.75.237.105 port 40280 ssh2
Feb 25 22:14:35 vpn sshd[21488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.75.237.105
2020-01-05 18:00:34
66.84.140.25 attack
Feb 24 05:45:39 vpn sshd[30623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.84.140.25
Feb 24 05:45:41 vpn sshd[30623]: Failed password for invalid user teamspeak2 from 66.84.140.25 port 60703 ssh2
Feb 24 05:49:42 vpn sshd[30628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.84.140.25
2020-01-05 17:59:51
67.205.189.175 attackbots
Jan  1 16:16:08 vpn sshd[14339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.189.175
Jan  1 16:16:10 vpn sshd[14339]: Failed password for invalid user serverpilot from 67.205.189.175 port 56944 ssh2
Jan  1 16:16:44 vpn sshd[14341]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.189.175
2020-01-05 17:42:57
67.187.30.77 attack
Mar 22 23:04:22 vpn sshd[28968]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.187.30.77
Mar 22 23:04:24 vpn sshd[28968]: Failed password for invalid user pawel from 67.187.30.77 port 50346 ssh2
Mar 22 23:08:42 vpn sshd[28995]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.187.30.77
2020-01-05 17:53:25

Recently Reported IPs

141.30.12.7 122.75.82.53 13.77.118.146 217.194.235.193
182.239.139.190 22.5.169.47 93.174.64.100 51.146.75.14
81.149.8.94 18.236.3.45 86.45.183.46 17.24.78.243
10.4.18.65 0.65.63.70 45.19.124.157 103.170.83.70
54.31.32.35 91.239.149.169 0.179.30.28 226.217.44.32