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

;; QUESTION SECTION:
;135.148.130.216.		IN	A

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

;; Query time: 131 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 03:57:15 CST 2022
;; MSG SIZE  rcvd: 108
Host info
216.130.148.135.in-addr.arpa domain name pointer ip216.ip-135-148-130.us.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
216.130.148.135.in-addr.arpa	name = ip216.ip-135-148-130.us.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
110.5.8.95 attackbotsspam
Unauthorized connection attempt detected from IP address 110.5.8.95 to port 23 [T]
2020-01-17 08:34:06
111.229.134.68 attackspambots
Unauthorized connection attempt detected from IP address 111.229.134.68 to port 2220 [J]
2020-01-17 09:00:50
179.96.62.29 attack
Jan 16 23:57:22 debian-2gb-nbg1-2 kernel: \[1474736.993327\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=179.96.62.29 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=21796 PROTO=TCP SPT=54245 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-17 08:49:03
218.22.105.162 attack
Unauthorized connection attempt detected from IP address 218.22.105.162 to port 3389 [T]
2020-01-17 08:45:46
116.105.100.235 attackbots
Unauthorized connection attempt detected from IP address 116.105.100.235 to port 23 [J]
2020-01-17 08:31:29
49.89.5.106 attackbotsspam
Unauthorized connection attempt detected from IP address 49.89.5.106 to port 80 [T]
2020-01-17 08:37:39
164.52.36.237 attackbotsspam
Unauthorized connection attempt detected from IP address 164.52.36.237 to port 6665 [J]
2020-01-17 08:50:12
121.34.33.87 attack
Unauthorized connection attempt detected from IP address 121.34.33.87 to port 445 [T]
2020-01-17 08:55:01
120.79.101.224 attackbots
Unauthorized connection attempt detected from IP address 120.79.101.224 to port 22 [T]
2020-01-17 08:29:08
176.113.115.51 attackbotsspam
Unauthorized connection attempt detected from IP address 176.113.115.51 to port 3389 [T]
2020-01-17 08:49:35
220.191.249.136 attackbotsspam
Unauthorized connection attempt detected from IP address 220.191.249.136 to port 1433 [T]
2020-01-17 08:44:24
119.123.200.49 attackspambots
Unauthorized connection attempt detected from IP address 119.123.200.49 to port 445 [T]
2020-01-17 08:29:49
111.38.107.127 attack
Unauthorized connection attempt detected from IP address 111.38.107.127 to port 81 [J]
2020-01-17 09:01:25
111.122.175.73 attackbotsspam
Unauthorized connection attempt detected from IP address 111.122.175.73 to port 1433 [T]
2020-01-17 09:01:01
222.187.237.15 attack
Unauthorized connection attempt detected from IP address 222.187.237.15 to port 23 [J]
2020-01-17 08:42:42

Recently Reported IPs

135.125.6.207 135.125.7.118 135.125.38.32 135.125.91.49
135.125.97.116 135.148.152.43 135.148.137.203 135.148.195.193
135.148.59.66 135.148.66.110 135.148.97.182 135.148.83.116
135.180.139.14 135.181.11.119 135.181.111.48 135.181.11.236
135.181.112.158 135.181.112.161 135.181.125.9 135.181.125.110