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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;247.55.66.140.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 20:27:35 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 140.66.55.247.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 140.66.55.247.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.59.211.245 attack
(sshd) Failed SSH login from 139.59.211.245 (DE/Germany/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: May  6 18:29:16 srv sshd[12256]: Invalid user peer from 139.59.211.245 port 50050
May  6 18:29:19 srv sshd[12256]: Failed password for invalid user peer from 139.59.211.245 port 50050 ssh2
May  6 18:40:44 srv sshd[12559]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245  user=root
May  6 18:40:46 srv sshd[12559]: Failed password for root from 139.59.211.245 port 47350 ssh2
May  6 18:48:49 srv sshd[13463]: Invalid user mir from 139.59.211.245 port 57544
2020-05-07 01:58:03
51.75.52.127 attackspambots
Unauthorized connection attempt detected from IP address 51.75.52.127 to port 806
2020-05-07 02:21:28
206.189.173.85 attackbotsspam
May  6 14:47:34 debian-2gb-nbg1-2 kernel: \[11028144.091868\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=206.189.173.85 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=44059 PROTO=TCP SPT=41698 DPT=9071 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-07 02:28:00
139.162.23.47 attackspam
Fail2Ban Ban Triggered
2020-05-07 01:57:30
185.153.199.52 attackbotsspam
Multi-port scan [Probing]
2020-05-07 02:08:40
45.143.220.151 attackspambots
[MK-Root1] Blocked by UFW
2020-05-07 02:22:43
125.64.94.220 attackbots
[21:00:38] (YnM): [21:00:36] Telnet connection: 125.64.94.220/49200
[21:00:39] (YnM): [21:00:36] EOF ident connection
[21:00:39] (YnM): [21:00:36] Refused telnet@125.64.94.220 (invalid handle: GET / HTTP/1.0)
2020-05-07 02:12:39
172.104.242.173 attackbotsspam
Trying ports that it shouldn't be.
2020-05-07 02:10:56
192.241.230.228 attackspam
05/06/2020-08:37:33.595907 192.241.230.228 Protocol: 17 GPL SQL ping attempt
2020-05-07 02:31:07
45.56.91.118 attackbotsspam
Unauthorized connection attempt from IP address 45.56.91.118 on Port 3389(RDP)
2020-05-07 02:24:57
185.175.93.6 attack
05/06/2020-13:41:25.091902 185.175.93.6 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-05-07 02:08:12
162.251.236.2 attack
probes 8 times on the port 13818
2020-05-07 01:53:47
113.214.30.171 attack
" "
2020-05-07 02:14:16
185.200.118.85 attack
scans once in preceeding hours on the ports (in chronological order) 1723 resulting in total of 5 scans from 185.200.118.0/24 block.
2020-05-07 02:04:14
185.175.93.18 attackspambots
05/06/2020-13:47:20.330196 185.175.93.18 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-05-07 02:07:41

Recently Reported IPs

55.244.254.237 52.197.35.210 150.237.114.109 50.71.212.142
174.163.35.36 221.167.0.192 78.84.20.214 166.167.77.57
72.128.220.231 85.27.194.162 59.91.17.82 115.33.187.39
237.221.60.244 68.186.64.52 61.221.108.132 78.183.153.28
155.76.32.103 166.95.165.187 220.9.120.181 170.121.19.229