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.45.28 attackbotsspam
Unauthorized connection attempt from IP address 49.49.45.28 on Port 445(SMB)
2020-08-31 23:32:50
49.49.45.89 attackbots
Unauthorised access (Aug  7) SRC=49.49.45.89 LEN=52 TOS=0x10 PREC=0x40 TTL=113 ID=10200 DF TCP DPT=445 WINDOW=8192 SYN
2020-08-07 14:50:50
49.49.45.237 attackspambots
Mar 10 10:07:38 pl3server sshd[32621]: Did not receive identification string from 49.49.45.237
Mar 10 10:07:45 pl3server sshd[352]: reveeclipse mapping checking getaddrinfo for mx-ll-49.49.45-237.dynamic.3bb.co.th [49.49.45.237] failed - POSSIBLE BREAK-IN ATTEMPT!
Mar 10 10:07:45 pl3server sshd[352]: Invalid user nagesh from 49.49.45.237
Mar 10 10:07:45 pl3server sshd[352]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.49.45.237


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.49.45.237
2020-03-10 22:19:08
49.49.42.50 attackbotsspam
Unauthorized connection attempt detected from IP address 49.49.42.50 to port 5555 [J]
2020-01-20 18:53:31
49.49.46.189 attackbotsspam
Unauthorized connection attempt from IP address 49.49.46.189 on Port 445(SMB)
2019-12-19 04:22:37
49.49.44.21 attackspam
port scan and connect, tcp 23 (telnet)
2019-12-03 18:02:57
49.49.45.220 attack
firewall-block, port(s): 26/tcp
2019-11-30 15:17:28
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.49.4.126
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52460
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.49.4.126.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 12:35:26 CST 2022
;; MSG SIZE  rcvd: 104
Host info
126.4.49.49.in-addr.arpa domain name pointer mx-ll-49.49.4-126.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
126.4.49.49.in-addr.arpa	name = mx-ll-49.49.4-126.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.247.214.67 attack
Dec 13 15:16:46 MK-Soft-Root1 sshd[17068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.247.214.67 
Dec 13 15:16:48 MK-Soft-Root1 sshd[17068]: Failed password for invalid user lipps from 49.247.214.67 port 43350 ssh2
...
2019-12-13 22:31:36
82.64.19.17 attackspambots
SSH brute-force: detected 8 distinct usernames within a 24-hour window.
2019-12-13 22:11:14
27.254.130.69 attackspambots
$f2bV_matches
2019-12-13 22:20:57
203.195.201.128 attackspambots
Dec 13 03:50:12 wbs sshd\[23738\]: Invalid user host from 203.195.201.128
Dec 13 03:50:12 wbs sshd\[23738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.201.128
Dec 13 03:50:14 wbs sshd\[23738\]: Failed password for invalid user host from 203.195.201.128 port 56876 ssh2
Dec 13 03:55:47 wbs sshd\[24266\]: Invalid user ammie from 203.195.201.128
Dec 13 03:55:47 wbs sshd\[24266\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.201.128
2019-12-13 22:03:13
107.175.33.240 attackspambots
Dec 13 15:45:27 DAAP sshd[10052]: Invalid user ubuntu from 107.175.33.240 port 57160
Dec 13 15:45:27 DAAP sshd[10052]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.175.33.240
Dec 13 15:45:27 DAAP sshd[10052]: Invalid user ubuntu from 107.175.33.240 port 57160
Dec 13 15:45:29 DAAP sshd[10052]: Failed password for invalid user ubuntu from 107.175.33.240 port 57160 ssh2
...
2019-12-13 22:47:15
88.230.168.131 attackspambots
SSH bruteforce
2019-12-13 22:08:50
85.192.35.167 attack
Dec 13 12:49:35 ns382633 sshd\[24952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.192.35.167  user=root
Dec 13 12:49:37 ns382633 sshd\[24952\]: Failed password for root from 85.192.35.167 port 52772 ssh2
Dec 13 12:57:58 ns382633 sshd\[26459\]: Invalid user kojiya from 85.192.35.167 port 33452
Dec 13 12:57:58 ns382633 sshd\[26459\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.192.35.167
Dec 13 12:58:00 ns382633 sshd\[26459\]: Failed password for invalid user kojiya from 85.192.35.167 port 33452 ssh2
2019-12-13 22:31:06
144.217.40.3 attackspam
Dec 13 04:26:38 eddieflores sshd\[15271\]: Invalid user liam from 144.217.40.3
Dec 13 04:26:38 eddieflores sshd\[15271\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip3.ip-144-217-40.net
Dec 13 04:26:40 eddieflores sshd\[15271\]: Failed password for invalid user liam from 144.217.40.3 port 33358 ssh2
Dec 13 04:32:10 eddieflores sshd\[15762\]: Invalid user http from 144.217.40.3
Dec 13 04:32:10 eddieflores sshd\[15762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip3.ip-144-217-40.net
2019-12-13 22:46:40
45.143.220.76 attack
Dec 13 16:59:14 debian-2gb-vpn-nbg1-1 kernel: [623931.533455] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=45.143.220.76 DST=78.46.192.101 LEN=443 TOS=0x00 PREC=0x00 TTL=54 ID=25782 DF PROTO=UDP SPT=5062 DPT=5060 LEN=423
2019-12-13 22:18:33
217.113.3.94 attack
port scan and connect, tcp 1433 (ms-sql-s)
2019-12-13 22:24:54
186.13.103.241 attack
Dec 13 08:43:00 debian-2gb-nbg1-2 kernel: \[24504514.202052\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=186.13.103.241 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=47 ID=58980 PROTO=TCP SPT=34617 DPT=23 WINDOW=27081 RES=0x00 SYN URGP=0
2019-12-13 22:05:25
68.183.134.134 attack
xmlrpc attack
2019-12-13 22:38:21
106.13.4.172 attackbots
2019-12-08 07:10:57,282 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 07:34:11,885 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 07:55:24,975 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 08:17:04,968 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
2019-12-08 08:38:47,867 fail2ban.actions        \[3073\]: NOTICE  \[ssh\] Ban 106.13.4.172
...
2019-12-13 22:07:24
128.199.211.110 attackspam
2019-12-13T13:20:06.832680shield sshd\[6463\]: Invalid user macgeh from 128.199.211.110 port 39581
2019-12-13T13:20:06.837259shield sshd\[6463\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.211.110
2019-12-13T13:20:08.779646shield sshd\[6463\]: Failed password for invalid user macgeh from 128.199.211.110 port 39581 ssh2
2019-12-13T13:27:26.672562shield sshd\[7862\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.211.110  user=root
2019-12-13T13:27:28.017983shield sshd\[7862\]: Failed password for root from 128.199.211.110 port 43733 ssh2
2019-12-13 22:38:09
178.128.226.2 attackbots
$f2bV_matches
2019-12-13 22:22:29

Recently Reported IPs

39.115.85.32 174.75.211.222 154.72.170.206 5.235.233.100
200.78.196.224 221.15.147.228 154.5.171.229 186.192.177.30
114.119.137.224 14.21.7.210 109.86.245.168 43.225.169.157
80.146.191.222 112.66.202.172 38.77.11.246 47.90.202.218
182.74.131.154 106.14.140.165 117.196.52.55 170.254.204.217