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:
IP Type Details Datetime
116.0.1.138 attack
Jul2305:47:05server2pure-ftpd:\(\?@116.0.1.138\)[WARNING]Authenticationfailedforuser[anonymous]Jul2305:48:49server2pure-ftpd:\(\?@116.0.1.138\)[WARNING]Authenticationfailedforuser[www]Jul2305:50:23server2pure-ftpd:\(\?@116.0.1.138\)[WARNING]Authenticationfailedforuser[www]Jul2305:51:03server2pure-ftpd:\(\?@116.0.1.138\)[WARNING]Authenticationfailedforuser[www]Jul2305:51:19server2pure-ftpd:\(\?@116.0.1.138\)[WARNING]Authenticationfailedforuser[www]
2020-07-23 18:32:54
116.0.1.250 attackbotsspam
Unauthorized connection attempt from IP address 116.0.1.250 on Port 445(SMB)
2020-01-31 15:55:29
116.0.134.123 attack
Scanning
2019-12-31 21:11:45
116.0.148.155 attack
Unauthorised access (Sep 21) SRC=116.0.148.155 LEN=40 TTL=47 ID=60302 TCP DPT=8080 WINDOW=22 SYN
2019-09-21 14:00:45
116.0.196.133 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-08-29 20:32:45
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 116.0.1.98
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24320
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;116.0.1.98.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 02:08:22 CST 2022
;; MSG SIZE  rcvd: 103
Host info
Host 98.1.0.116.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 98.1.0.116.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
179.106.69.179 attackspambots
unauthorized connection attempt
2020-01-22 20:10:49
202.43.146.107 attack
Unauthorized connection attempt detected from IP address 202.43.146.107 to port 2220 [J]
2020-01-22 20:36:16
51.75.206.42 attack
Unauthorized connection attempt detected from IP address 51.75.206.42 to port 2220 [J]
2020-01-22 20:07:05
141.237.78.242 attack
unauthorized connection attempt
2020-01-22 20:26:40
87.12.243.48 attackbotsspam
unauthorized connection attempt
2020-01-22 20:32:33
180.116.26.80 attackbots
unauthorized connection attempt
2020-01-22 20:26:14
62.16.57.137 attackspam
unauthorized connection attempt
2020-01-22 20:03:36
117.92.120.236 attack
unauthorized connection attempt
2020-01-22 20:20:28
113.181.14.150 attackbotsspam
unauthorized connection attempt
2020-01-22 19:59:23
103.242.155.189 attackbots
unauthorized connection attempt
2020-01-22 19:59:48
121.25.49.37 attack
unauthorized connection attempt
2020-01-22 19:56:49
223.16.91.11 attackspam
unauthorized connection attempt
2020-01-22 20:25:07
119.51.31.133 attack
[portscan] tcp/23 [TELNET]
*(RWIN=3796)(01221303)
2020-01-22 19:57:20
188.217.250.154 attackbots
Unauthorized connection attempt detected from IP address 188.217.250.154 to port 8080 [J]
2020-01-22 20:16:44
218.21.170.244 attack
Unauthorized connection attempt detected from IP address 218.21.170.244 to port 8080 [J]
2020-01-22 20:05:57

Recently Reported IPs

44.179.121.253 116.0.106.206 116.0.106.212 116.0.20.24
116.0.22.33 116.0.54.55 116.1.255.142 116.1.3.67
116.1.42.46 11.26.61.163 116.114.184.59 116.114.66.2
116.115.61.45 116.116.117.104 116.116.117.120 116.116.203.160
116.116.203.25 173.21.139.97 116.116.203.8 116.116.64.115