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

;; QUESTION SECTION:
;114.138.106.249.		IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 14:52:42 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 249.106.138.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 249.106.138.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
80.82.77.245 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-17 02:33:25
192.241.246.50 attackbotsspam
Nov 16 19:00:27 sso sshd[26714]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.246.50
Nov 16 19:00:28 sso sshd[26714]: Failed password for invalid user ts3bot from 192.241.246.50 port 36257 ssh2
...
2019-11-17 02:39:08
178.128.81.60 attackbots
Nov 16 19:26:17 ext1 sshd[6065]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.81.60
2019-11-17 02:31:03
34.77.225.12 attack
firewall-block, port(s): 3306/tcp
2019-11-17 02:33:44
18.224.62.89 attackspam
Port Scan: TCP/443
2019-11-17 02:59:25
194.182.65.100 attack
Nov 16 18:27:13 ip-172-31-62-245 sshd\[19179\]: Invalid user beta12 from 194.182.65.100\
Nov 16 18:27:15 ip-172-31-62-245 sshd\[19179\]: Failed password for invalid user beta12 from 194.182.65.100 port 41248 ssh2\
Nov 16 18:30:44 ip-172-31-62-245 sshd\[19188\]: Invalid user wardoff from 194.182.65.100\
Nov 16 18:30:46 ip-172-31-62-245 sshd\[19188\]: Failed password for invalid user wardoff from 194.182.65.100 port 49458 ssh2\
Nov 16 18:34:24 ip-172-31-62-245 sshd\[19196\]: Invalid user phillip from 194.182.65.100\
2019-11-17 03:05:28
93.33.198.25 attack
Automatic report - Port Scan Attack
2019-11-17 03:02:05
45.89.140.112 attack
Nov 15 00:05:57 l01 sshd[496731]: reveeclipse mapping checking getaddrinfo for kollhdxdlp [45.89.140.112] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 15 00:05:57 l01 sshd[496731]: Invalid user koeninger from 45.89.140.112
Nov 15 00:05:57 l01 sshd[496731]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.89.140.112 
Nov 15 00:06:00 l01 sshd[496731]: Failed password for invalid user koeninger from 45.89.140.112 port 51544 ssh2
Nov 15 00:10:09 l01 sshd[497156]: reveeclipse mapping checking getaddrinfo for kollhdxdlp [45.89.140.112] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 15 00:10:09 l01 sshd[497156]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.89.140.112  user=r.r
Nov 15 00:10:11 l01 sshd[497156]: Failed password for r.r from 45.89.140.112 port 37968 ssh2
Nov 15 00:14:46 l01 sshd[497589]: reveeclipse mapping checking getaddrinfo for kollhdxdlp [45.89.140.112] failed - POSSIBLE BREAK-IN ATT........
-------------------------------
2019-11-17 03:06:50
180.251.53.32 attackbots
B: Magento admin pass test (wrong country)
2019-11-17 03:03:45
182.61.37.144 attack
SSH Bruteforce attempt
2019-11-17 02:30:49
217.182.252.161 attackspambots
2019-11-16T18:38:14.058507abusebot-2.cloudsearch.cf sshd\[15565\]: Invalid user atantee from 217.182.252.161 port 49572
2019-11-17 02:49:19
122.227.26.90 attackspam
SSH Bruteforce attack
2019-11-17 02:54:12
193.29.13.20 attackspam
Fail2Ban Ban Triggered
2019-11-17 03:01:41
118.25.8.128 attackbots
SSH Brute-Force reported by Fail2Ban
2019-11-17 02:46:51
1.34.177.166 attack
Unauthorised access (Nov 16) SRC=1.34.177.166 LEN=40 PREC=0x20 TTL=51 ID=27317 TCP DPT=23 WINDOW=26874 SYN
2019-11-17 02:34:33

Recently Reported IPs

114.138.68.180 114.138.247.148 114.138.82.108 114.139.126.75
114.139.159.121 114.139.151.250 114.139.110.155 114.138.25.10
114.139.108.178 114.139.168.230 114.139.169.142 114.139.169.50
113.53.106.234 114.139.170.183 114.139.170.148 114.139.159.201
114.139.171.189 114.139.173.20 114.139.172.168 114.139.169.120