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

Region: Bangkok

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.49.166.134
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56604
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.49.166.134.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 24 09:10:15 CST 2025
;; MSG SIZE  rcvd: 106
Host info
134.166.49.49.in-addr.arpa domain name pointer mx-ll-49.49.166-134.dynamic.3bb.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
134.166.49.49.in-addr.arpa	name = mx-ll-49.49.166-134.dynamic.3bb.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
117.50.74.34 attackbots
2019-10-01T00:07:09.301899hub.schaetter.us sshd\[9728\]: Invalid user ketav from 117.50.74.34 port 59865
2019-10-01T00:07:09.307686hub.schaetter.us sshd\[9728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.74.34
2019-10-01T00:07:11.713123hub.schaetter.us sshd\[9728\]: Failed password for invalid user ketav from 117.50.74.34 port 59865 ssh2
2019-10-01T00:10:48.542257hub.schaetter.us sshd\[9740\]: Invalid user manager from 117.50.74.34 port 44191
2019-10-01T00:10:48.552414hub.schaetter.us sshd\[9740\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.74.34
...
2019-10-01 08:43:36
93.188.34.101 attack
[portscan] Port scan
2019-10-01 08:17:11
148.70.65.131 attack
$f2bV_matches
2019-10-01 08:14:43
81.28.167.30 attackspam
Sep 30 22:54:31 vpn01 sshd[10608]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.28.167.30
Sep 30 22:54:33 vpn01 sshd[10608]: Failed password for invalid user elision from 81.28.167.30 port 36084 ssh2
...
2019-10-01 08:52:47
142.93.240.79 attackspambots
Sep 30 13:55:55 hanapaa sshd\[13237\]: Invalid user pass from 142.93.240.79
Sep 30 13:55:55 hanapaa sshd\[13237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.240.79
Sep 30 13:55:57 hanapaa sshd\[13237\]: Failed password for invalid user pass from 142.93.240.79 port 59900 ssh2
Sep 30 14:00:32 hanapaa sshd\[13616\]: Invalid user passwd from 142.93.240.79
Sep 30 14:00:32 hanapaa sshd\[13616\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.240.79
2019-10-01 08:15:12
119.90.61.10 attackbots
2019-10-01T00:06:21.370151abusebot-7.cloudsearch.cf sshd\[24977\]: Invalid user bernd from 119.90.61.10 port 41192
2019-10-01 08:36:22
45.136.109.186 attack
09/30/2019-18:27:08.276969 45.136.109.186 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-01 08:47:19
134.209.221.69 attackspambots
port scan and connect, tcp 23 (telnet)
2019-10-01 08:30:03
138.197.213.233 attackbotsspam
2019-10-01T03:17:58.065964tmaserv sshd\[2455\]: Invalid user password from 138.197.213.233 port 43064
2019-10-01T03:17:58.071576tmaserv sshd\[2455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.213.233
2019-10-01T03:18:00.239738tmaserv sshd\[2455\]: Failed password for invalid user password from 138.197.213.233 port 43064 ssh2
2019-10-01T03:22:08.306664tmaserv sshd\[2735\]: Invalid user interalt from 138.197.213.233 port 46328
2019-10-01T03:22:08.311595tmaserv sshd\[2735\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.213.233
2019-10-01T03:22:10.133780tmaserv sshd\[2735\]: Failed password for invalid user interalt from 138.197.213.233 port 46328 ssh2
...
2019-10-01 08:27:18
51.68.215.113 attackbotsspam
Oct  1 01:41:40 ns3110291 sshd\[11450\]: Invalid user vg from 51.68.215.113
Oct  1 01:41:42 ns3110291 sshd\[11450\]: Failed password for invalid user vg from 51.68.215.113 port 56200 ssh2
Oct  1 01:45:26 ns3110291 sshd\[11611\]: Invalid user jira from 51.68.215.113
Oct  1 01:45:28 ns3110291 sshd\[11611\]: Failed password for invalid user jira from 51.68.215.113 port 40708 ssh2
Oct  1 01:49:18 ns3110291 sshd\[11790\]: Invalid user maria from 51.68.215.113
...
2019-10-01 08:23:53
148.245.42.176 attackbots
*Port Scan* detected from 148.245.42.176 (MX/Mexico/na-42-176.static.avantel.net.mx). 4 hits in the last 160 seconds
2019-10-01 08:28:58
46.101.142.99 attackspam
Oct  1 02:49:46 server sshd\[18236\]: Invalid user test from 46.101.142.99 port 60340
Oct  1 02:49:46 server sshd\[18236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.142.99
Oct  1 02:49:49 server sshd\[18236\]: Failed password for invalid user test from 46.101.142.99 port 60340 ssh2
Oct  1 02:54:37 server sshd\[16890\]: Invalid user a4abroad from 46.101.142.99 port 53296
Oct  1 02:54:37 server sshd\[16890\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.142.99
2019-10-01 08:20:05
85.214.36.244 attackspambots
SSH Bruteforce attempt
2019-10-01 08:41:53
165.227.49.242 attackbotsspam
Sep 30 23:53:59 XXXXXX sshd[3472]: Invalid user wp-user from 165.227.49.242 port 36057
2019-10-01 08:48:32
41.35.88.120 attack
Chat Spam
2019-10-01 08:40:34

Recently Reported IPs

25.30.172.57 22.122.84.121 239.140.217.174 147.24.64.22
167.23.30.226 235.201.252.239 250.98.227.89 190.109.113.161
50.91.226.24 165.188.144.243 144.170.211.46 201.29.204.175
60.100.116.35 255.157.61.32 25.36.193.230 54.226.84.36
5.162.247.62 97.242.195.96 196.155.35.20 186.219.100.24