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

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
114.119.148.168 attackbots
badbot
2020-01-14 03:47:39
114.119.148.80 attackspambots
badbot
2020-01-13 22:47:54
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.119.148.132
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55954
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;114.119.148.132.		IN	A

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

;; Query time: 106 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 06:01:47 CST 2022
;; MSG SIZE  rcvd: 108
Host info
132.148.119.114.in-addr.arpa domain name pointer petalbot-114-119-148-132.petalsearch.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
132.148.119.114.in-addr.arpa	name = petalbot-114-119-148-132.petalsearch.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
138.255.0.27 attackbots
Invalid user test12 from 138.255.0.27 port 41314
2020-04-22 15:27:29
128.199.118.27 attackbotsspam
(sshd) Failed SSH login from 128.199.118.27 (SG/Singapore/-): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 22 06:35:45 ubnt-55d23 sshd[22728]: Invalid user ou from 128.199.118.27 port 55308
Apr 22 06:35:47 ubnt-55d23 sshd[22728]: Failed password for invalid user ou from 128.199.118.27 port 55308 ssh2
2020-04-22 15:02:58
37.187.244.128 attackspam
Apr 22 01:09:40 server1 sshd\[18228\]: Invalid user gittest from 37.187.244.128
Apr 22 01:09:40 server1 sshd\[18228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.244.128 
Apr 22 01:09:42 server1 sshd\[18228\]: Failed password for invalid user gittest from 37.187.244.128 port 47090 ssh2
Apr 22 01:13:42 server1 sshd\[19364\]: Invalid user nz from 37.187.244.128
Apr 22 01:13:42 server1 sshd\[19364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.244.128 
...
2020-04-22 15:20:43
175.149.118.180 attack
Unauthorized connection attempt detected from IP address 175.149.118.180 to port 23 [T]
2020-04-22 15:04:20
118.174.113.237 attackspam
Automatic report - SSH Brute-Force Attack
2020-04-22 15:15:50
185.183.243.118 attackbotsspam
Apr 22 05:53:26  sshd\[17870\]: User root from 185.183.243.118 not allowed because not listed in AllowUsersApr 22 05:53:28  sshd\[17870\]: Failed password for invalid user root from 185.183.243.118 port 50186 ssh2
...
2020-04-22 15:26:15
184.169.107.7 attackbots
Brute forcing email accounts
2020-04-22 15:23:10
120.92.34.203 attackbots
Invalid user nm from 120.92.34.203 port 38048
2020-04-22 15:05:51
104.244.79.28 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-04-22 15:32:33
103.94.180.253 attack
Attack, like DDOS, Brute-Force, Port Scan, Hack, etc.
2020-04-22 15:16:28
140.186.20.218 attack
Brute forcing email accounts
2020-04-22 15:29:59
86.62.5.233 attack
Unauthorized connection attempt detected from IP address 86.62.5.233 to port 23 [T]
2020-04-22 15:07:42
188.166.8.178 attackbotsspam
$f2bV_matches
2020-04-22 15:08:42
129.211.49.17 attack
Invalid user ubuntu from 129.211.49.17 port 58132
2020-04-22 14:53:53
49.233.215.214 attackbots
Invalid user test1 from 49.233.215.214 port 58778
2020-04-22 15:07:19

Recently Reported IPs

114.119.148.154 114.119.148.198 114.119.148.233 114.119.148.242
114.119.148.202 114.119.148.208 114.119.148.34 114.119.148.4
114.119.148.47 114.119.149.171 114.119.148.49 114.119.149.218
114.119.149.83 114.119.149.91 114.119.150.190 114.119.150.32
114.119.150.56 114.119.151.156 114.119.151.170 114.119.151.50