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

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

;; QUESTION SECTION:
;114.239.45.52.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 01:06:34 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 52.45.239.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 52.45.239.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
52.232.246.89 attackspam
May 16 21:32:55 Host-KEWR-E sshd[779]: User root from 52.232.246.89 not allowed because not listed in AllowUsers
...
2020-05-19 23:38:49
190.156.227.27 attack
Unauthorized login to one of my accounts from this IP, probably taking advantage of one of the many data breaches out there
2020-05-18 05:05:43
201.161.41.142 attack
201.161.41.142 - - [17/May/2020:10:33:51 +0800] "host" "GET /w00tw00t.at.ISC.SANS.DFind:) HTTP/1.1" 400 570 "-" "-" "-"
2020-05-17 15:20:55
112.64.136.62 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:40:14
94.102.51.16 attack
May 17 01:20:39 debian-2gb-nbg1-2 kernel: \[11930081.442784\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.51.16 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=52748 PROTO=TCP SPT=45854 DPT=3975 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-17 08:44:45
161.35.97.115 attackbotsspam
ET WEB_SERVER PyCurl Suspicious User Agent Inbound - port: 80 proto: TCP cat: Attempted Information Leak
2020-05-17 08:37:42
51.178.86.49 attackspambots
2020-05-19T11:30:58.576503scmdmz1 sshd[16530]: Invalid user pbk from 51.178.86.49 port 35610
2020-05-19T11:31:00.507836scmdmz1 sshd[16530]: Failed password for invalid user pbk from 51.178.86.49 port 35610 ssh2
2020-05-19T11:37:20.237987scmdmz1 sshd[17559]: Invalid user afb from 51.178.86.49 port 41136
...
2020-05-19 23:42:42
60.246.2.153 attack
(imapd) Failed IMAP login from 60.246.2.153 (MO/Macao/nz2l153.bb60246.ctm.net): 1 in the last 3600 secs
2020-05-19 23:50:11
94.102.50.144 attackspambots
4389/tcp 8389/tcp 2389/tcp...
[2020-04-22/05-16]489pkt,207pt.(tcp)
2020-05-17 08:45:08
118.193.159.139 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:39:52
94.102.51.29 attackspambots
May 17 02:27:20 debian-2gb-nbg1-2 kernel: \[11934082.191308\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=94.102.51.29 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=293 PROTO=TCP SPT=40571 DPT=5000 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-17 08:43:43
178.46.136.122 attack
(imapd) Failed IMAP login from 178.46.136.122 (RU/Russia/ip-178-46-136-122.dsl.surnet.ru): 1 in the last 3600 secs
2020-05-19 23:43:17
185.143.223.244 attackbots
firewall-block, port(s): 3395/tcp, 3397/tcp
2020-05-17 08:35:50
104.206.128.74 attack
 TCP (SYN) 104.206.128.74:60254 -> port 21, len 44
2020-05-17 08:40:44
94.102.51.28 attackbots
TCP ports : 833 / 23833 / 28633 / 32633 / 53633 / 55233
2020-05-17 08:44:00

Recently Reported IPs

102.40.98.94 102.41.87.146 102.42.211.145 102.42.33.182
102.43.86.177 102.43.82.112 102.44.168.237 102.43.46.8
114.239.45.54 114.239.45.60 103.1.238.214 103.1.237.69
103.1.12.179 103.100.211.228 103.1.221.32 103.1.187.139
103.1.92.101 103.101.153.30 103.102.234.214 114.239.45.63