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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 136.243.148.9
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63628
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;136.243.148.9.			IN	A

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

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

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
119.28.105.127 attackbots
SSH Brute Force
2019-11-28 03:03:10
124.158.7.220 attackspam
" "
2019-11-28 03:05:47
51.79.65.158 attackspambots
2019-11-27T17:25:20.553991scmdmz1 sshd\[6496\]: Invalid user hawaka from 51.79.65.158 port 39218
2019-11-27T17:25:20.556673scmdmz1 sshd\[6496\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.ip-51-79-65.net
2019-11-27T17:25:21.837906scmdmz1 sshd\[6496\]: Failed password for invalid user hawaka from 51.79.65.158 port 39218 ssh2
...
2019-11-28 02:33:00
103.49.249.42 attackbots
Nov 27 19:15:40 sd-53420 sshd\[15876\]: Invalid user king from 103.49.249.42
Nov 27 19:15:40 sd-53420 sshd\[15876\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.49.249.42
Nov 27 19:15:42 sd-53420 sshd\[15876\]: Failed password for invalid user king from 103.49.249.42 port 58172 ssh2
Nov 27 19:15:44 sd-53420 sshd\[15876\]: Failed password for invalid user king from 103.49.249.42 port 58172 ssh2
Nov 27 19:15:45 sd-53420 sshd\[15876\]: Failed password for invalid user king from 103.49.249.42 port 58172 ssh2
...
2019-11-28 02:36:09
167.114.0.23 attack
SSH Brute Force, server-1 sshd[5193]: Failed password for invalid user webmaster from 167.114.0.23 port 49064 ssh2
2019-11-28 02:57:17
195.246.57.2 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-28 03:02:50
118.178.119.198 attackspam
2019-11-27T18:08:24.713192abusebot-3.cloudsearch.cf sshd\[31975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.178.119.198  user=root
2019-11-28 02:35:52
104.37.169.192 attack
SSH Brute Force, server-1 sshd[5158]: Failed password for root from 104.37.169.192 port 60516 ssh2
2019-11-28 03:00:53
180.76.98.239 attackbots
SSH brute-force: detected 7 distinct usernames within a 24-hour window.
2019-11-28 02:56:55
222.169.185.251 attack
Nov 27 15:23:19 h1946882 sshd[1874]: reveeclipse mapping checking getaddrin=
fo for 251.185.169.222.broad.cc.jl.dynamic.163data.com.cn [222.169.185.=
251] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 27 15:23:19 h1946882 sshd[1874]: pam_unix(sshd:auth): authenticatio=
n failure; logname=3D uid=3D0 euid=3D0 tty=3Dssh ruser=3D rhost=3D222.1=
69.185.251  user=3Dbin
Nov 27 15:23:22 h1946882 sshd[1874]: Failed password for bin from 222.1=
69.185.251 port 44450 ssh2
Nov 27 15:23:22 h1946882 sshd[1874]: Received disconnect from 222.169.1=
85.251: 11: Bye Bye [preauth]
Nov 27 15:32:36 h1946882 sshd[1926]: reveeclipse mapping checking getaddrin=
fo for 251.185.169.222.broad.cc.jl.dynamic.163data.com.cn [222.169.185.=
251] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 27 15:32:36 h1946882 sshd[1926]: pam_unix(sshd:auth): authenticatio=
n failure; logname=3D uid=3D0 euid=3D0 tty=3Dssh ruser=3D rhost=3D222.1=
69.185.251=20
Nov 27 15:32:38 h1946882 sshd[1926]: Failed password for invalid user ........
-------------------------------
2019-11-28 02:41:33
195.3.146.88 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-28 02:43:28
49.235.173.198 attackbotsspam
REQUESTED PAGE: /wp-login.php
2019-11-28 02:44:18
195.254.134.194 attackbots
0,69-01/01 [bc01/m23] PostRequest-Spammer scoring: essen
2019-11-28 02:46:42
185.176.27.254 attackbotsspam
11/27/2019-13:32:08.307740 185.176.27.254 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-28 02:34:09
196.13.207.52 attackspambots
Nov 27 19:30:06 ns382633 sshd\[32553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.13.207.52  user=root
Nov 27 19:30:09 ns382633 sshd\[32553\]: Failed password for root from 196.13.207.52 port 60748 ssh2
Nov 27 19:44:48 ns382633 sshd\[2593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.13.207.52  user=root
Nov 27 19:44:51 ns382633 sshd\[2593\]: Failed password for root from 196.13.207.52 port 60562 ssh2
Nov 27 19:48:29 ns382633 sshd\[3393\]: Invalid user nagios from 196.13.207.52 port 39130
Nov 27 19:48:29 ns382633 sshd\[3393\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.13.207.52
2019-11-28 03:04:39

Recently Reported IPs

136.243.15.9 136.243.149.84 136.243.152.180 136.243.150.32
136.243.153.26 136.243.154.148 136.243.154.108 136.243.154.85
136.243.154.249 136.243.155.105 136.243.156.120 136.243.156.140
136.243.156.215 136.243.156.137 136.243.157.217 136.243.158.151
136.243.159.42 136.243.16.222 136.243.158.137 136.243.160.101