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

;; QUESTION SECTION:
;243.66.116.149.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 00:35:04 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 149.116.66.243.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 149.116.66.243.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
69.131.84.33 attackbotsspam
Nov 22 07:22:09 ns382633 sshd\[10386\]: Invalid user kare from 69.131.84.33 port 52600
Nov 22 07:22:09 ns382633 sshd\[10386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.131.84.33
Nov 22 07:22:11 ns382633 sshd\[10386\]: Failed password for invalid user kare from 69.131.84.33 port 52600 ssh2
Nov 22 07:29:15 ns382633 sshd\[11495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.131.84.33  user=root
Nov 22 07:29:17 ns382633 sshd\[11495\]: Failed password for root from 69.131.84.33 port 51692 ssh2
2019-11-22 15:17:26
187.188.193.211 attackbotsspam
Nov 22 07:30:56 km20725 sshd\[26336\]: Failed password for mysql from 187.188.193.211 port 38628 ssh2Nov 22 07:35:43 km20725 sshd\[26581\]: Invalid user marine from 187.188.193.211Nov 22 07:35:45 km20725 sshd\[26581\]: Failed password for invalid user marine from 187.188.193.211 port 45660 ssh2Nov 22 07:40:12 km20725 sshd\[26998\]: Invalid user sudkamp from 187.188.193.211
...
2019-11-22 15:26:57
27.255.77.221 attack
SASL broute force
2019-11-22 15:30:28
112.207.47.94 attackspam
Wordpress login attempts
2019-11-22 15:36:54
51.255.35.41 attackbotsspam
Nov 21 21:01:26 web9 sshd\[19506\]: Invalid user michalis from 51.255.35.41
Nov 21 21:01:26 web9 sshd\[19506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.35.41
Nov 21 21:01:29 web9 sshd\[19506\]: Failed password for invalid user michalis from 51.255.35.41 port 46113 ssh2
Nov 21 21:04:47 web9 sshd\[19940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.35.41  user=root
Nov 21 21:04:49 web9 sshd\[19940\]: Failed password for root from 51.255.35.41 port 35867 ssh2
2019-11-22 15:10:16
51.254.79.235 attackbotsspam
Nov 22 07:54:37 legacy sshd[22796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.79.235
Nov 22 07:54:39 legacy sshd[22796]: Failed password for invalid user test from 51.254.79.235 port 51172 ssh2
Nov 22 07:58:23 legacy sshd[22869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.79.235
...
2019-11-22 15:11:14
106.13.31.93 attackbots
(sshd) Failed SSH login from 106.13.31.93 (-): 5 in the last 3600 secs
2019-11-22 15:28:09
113.141.70.199 attackspambots
Nov 22 03:29:12 ws19vmsma01 sshd[198436]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.141.70.199
Nov 22 03:29:14 ws19vmsma01 sshd[198436]: Failed password for invalid user beryl from 113.141.70.199 port 44928 ssh2
...
2019-11-22 15:18:17
182.61.15.70 attackbotsspam
F2B jail: sshd. Time: 2019-11-22 08:03:59, Reported by: VKReport
2019-11-22 15:20:14
51.158.21.170 attackbots
" "
2019-11-22 15:13:01
85.133.159.146 attackspambots
2019-11-22 00:28:30 H=(85.133.159.146.pos-1-0.7tir.sepanta.net) [85.133.159.146]:39154 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/query/ip/85.133.159.146)
2019-11-22 00:28:32 H=(85.133.159.146.pos-1-0.7tir.sepanta.net) [85.133.159.146]:39154 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.3, 127.0.0.4) (https://www.spamhaus.org/query/ip/85.133.159.146)
2019-11-22 00:28:34 H=(85.133.159.146.pos-1-0.7tir.sepanta.net) [85.133.159.146]:39154 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.3, 127.0.0.4) (https://www.spamhaus.org/query/ip/85.133.159.146)
...
2019-11-22 15:38:42
54.36.189.105 attack
Nov 22 06:29:02 web8 sshd\[7113\]: Invalid user user from 54.36.189.105
Nov 22 06:29:02 web8 sshd\[7113\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.189.105
Nov 22 06:29:04 web8 sshd\[7113\]: Failed password for invalid user user from 54.36.189.105 port 42266 ssh2
Nov 22 06:29:07 web8 sshd\[7113\]: Failed password for invalid user user from 54.36.189.105 port 42266 ssh2
Nov 22 06:29:10 web8 sshd\[7113\]: Failed password for invalid user user from 54.36.189.105 port 42266 ssh2
2019-11-22 15:21:35
198.108.66.208 attack
Connection by 198.108.66.208 on port: 27017 got caught by honeypot at 11/22/2019 5:28:59 AM
2019-11-22 15:31:05
175.44.148.196 attackbotsspam
badbot
2019-11-22 15:13:27
14.102.107.117 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/14.102.107.117/ 
 
 IN - 1H : (26)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : IN 
 NAME ASN : ASN5 
 
 IP : 14.102.107.117 
 
 CIDR : 14.102.107.0/24 
 
 PREFIX COUNT : 9 
 
 UNIQUE IP COUNT : 3840 
 
 
 ATTACKS DETECTED ASN5 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-22 07:29:20 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-22 15:14:49

Recently Reported IPs

71.39.139.3 177.193.160.132 199.213.230.34 192.144.133.209
248.63.36.7 217.54.121.208 223.102.200.176 42.145.81.80
206.95.74.176 204.223.91.149 28.168.108.227 164.39.118.202
82.241.239.105 193.156.147.91 80.74.140.215 13.195.234.66
205.89.166.209 126.75.146.69 239.21.239.184 69.147.27.201