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: Germany

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
136.243.81.120 attackbotsspam
Sep  1 13:27:41 shivevps sshd[28086]: Bad protocol version identification '\024' from 136.243.81.120 port 43903
...
2020-09-02 03:41:22
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 136.243.81.46
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50614
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;136.243.81.46.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 11:48:22 CST 2022
;; MSG SIZE  rcvd: 106
Host info
46.81.243.136.in-addr.arpa domain name pointer static.46.81.243.136.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
46.81.243.136.in-addr.arpa	name = static.46.81.243.136.clients.your-server.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.173.35.45 attack
May 30 17:04:19 debian-2gb-nbg1-2 kernel: \[13109840.125627\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.173.35.45 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=239 ID=26531 PROTO=TCP SPT=54112 DPT=9443 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-31 04:06:54
221.235.79.162 attackbots
Unauthorized connection attempt detected from IP address 221.235.79.162 to port 8080
2020-05-31 04:36:13
177.94.30.208 attack
Unauthorized connection attempt detected from IP address 177.94.30.208 to port 23
2020-05-31 04:10:56
175.9.247.42 attackbotsspam
Unauthorized connection attempt detected from IP address 175.9.247.42 to port 23
2020-05-31 04:11:39
88.247.31.68 attackspambots
Unauthorized connection attempt detected from IP address 88.247.31.68 to port 85
2020-05-31 04:24:28
85.53.216.53 attackbots
Unauthorized connection attempt detected from IP address 85.53.216.53 to port 23
2020-05-31 04:25:07
36.32.3.46 attack
Unauthorized connection attempt detected from IP address 36.32.3.46 to port 8332
2020-05-31 04:33:25
122.14.196.133 attackspambots
Unauthorized connection attempt detected from IP address 122.14.196.133 to port 9196
2020-05-31 04:14:18
85.106.99.73 attack
Unauthorized connection attempt from IP address 85.106.99.73 on Port 445(SMB)
2020-05-31 04:38:23
177.96.176.126 attack
Unauthorized connection attempt detected from IP address 177.96.176.126 to port 23
2020-05-31 04:10:39
202.38.173.121 attackbotsspam
Unauthorized connection attempt detected from IP address 202.38.173.121 to port 22
2020-05-31 04:00:48
171.224.181.157 attackbots
Unauthorized connection attempt detected from IP address 171.224.181.157 to port 445
2020-05-31 04:12:12
183.131.113.53 attackbotsspam
Unauthorized connection attempt detected from IP address 183.131.113.53 to port 445
2020-05-31 04:08:23
187.8.54.170 attackspambots
Unauthorized connection attempt detected from IP address 187.8.54.170 to port 23
2020-05-31 04:06:00
112.232.151.170 attackbots
Unauthorized connection attempt detected from IP address 112.232.151.170 to port 2323
2020-05-31 04:19:32

Recently Reported IPs

136.243.81.254 136.243.82.147 136.243.82.201 136.243.84.74
136.243.89.230 136.243.89.250 136.243.84.75 136.243.9.112
136.243.87.179 136.243.90.254 136.243.9.196 136.243.89.227
136.243.92.92 136.243.93.72 136.243.90.34 136.243.93.90
136.243.95.150 136.243.97.28 136.243.95.84 136.244.107.239