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
137.226.113.10 attack
[N10.H2.VM2] Port Scanner Detected Blocked by UFW
2020-09-12 01:59:28
137.226.113.10 attackbots
Port scan denied
2020-09-11 17:50:45
137.226.113.56 attackbotsspam
4843/tcp 1883/tcp 8883/tcp...
[2020-06-14/08-11]44pkt,5pt.(tcp)
2020-08-12 07:49:20
137.226.113.56 attackspam
Unauthorized connection attempt detected from IP address 137.226.113.56 to port 4840 [T]
2020-07-20 06:50:01
137.226.113.56 attackbots
Port Scan
...
2020-07-14 02:14:02
137.226.113.9 attackspambots
port scan and connect, tcp 443 (https)
2020-06-06 21:06:05
137.226.113.56 attackbots
srv02 Mass scanning activity detected Target: 102(iso-tsap) ..
2020-06-01 20:17:23
137.226.113.27 attackbots
mozilla/5.0+zgrab/0.x+(compatible;+researchscan/t12sns;++http://researchscan.comsys.rwth-aachen.de)
2020-05-31 07:27:51
137.226.113.31 attackspambots
*Port Scan* detected from 137.226.113.31 (DE/Germany/researchscan23.comsys.rwth-aachen.de). 5 hits in the last 35 seconds
2020-05-25 17:19:31
137.226.113.10 attack
137.226.113.10
2020-04-14 12:57:11
137.226.113.56 attack
Apr 13 15:48:24 debian-2gb-nbg1-2 kernel: \[9044698.686856\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=137.226.113.56 DST=195.201.40.59 LEN=64 TOS=0x00 PREC=0x00 TTL=242 ID=54321 PROTO=TCP SPT=47703 DPT=102 WINDOW=65535 RES=0x00 SYN URGP=0
2020-04-14 01:14:48
137.226.113.56 attackbots
" "
2020-04-06 00:29:43
137.226.113.10 attack
Mar  5 21:51:17 debian-2gb-nbg1-2 kernel: \[5700646.129243\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=137.226.113.10 DST=195.201.40.59 LEN=1228 TOS=0x00 PREC=0x00 TTL=242 ID=54321 PROTO=UDP SPT=50832 DPT=443 LEN=1208
2020-03-06 05:32:53
137.226.113.56 attack
Unauthorized connection attempt detected from IP address 137.226.113.56 to port 102 [J]
2020-03-03 00:36:56
137.226.113.56 attackbots
Unauthorized connection attempt detected from IP address 137.226.113.56 to port 4840 [J]
2020-03-02 02:31:27
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 137.226.11.64
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8354
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;137.226.11.64.			IN	A

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

;; Query time: 83 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 12 10:14:35 CST 2022
;; MSG SIZE  rcvd: 106
Host info
64.11.226.137.in-addr.arpa domain name pointer kff64.ghi.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
64.11.226.137.in-addr.arpa	name = kff64.ghi.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
78.47.47.139 attack
Host Scan
2020-01-09 06:45:21
178.32.47.97 attackspambots
Jan  8 19:01:49 ws12vmsma01 sshd[27388]: Failed password for invalid user zmp from 178.32.47.97 port 35652 ssh2
Jan  8 19:09:23 ws12vmsma01 sshd[28412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.32.47.97  user=postgres
Jan  8 19:09:25 ws12vmsma01 sshd[28412]: Failed password for postgres from 178.32.47.97 port 51386 ssh2
...
2020-01-09 06:59:07
159.65.71.216 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-01-09 06:40:09
222.186.173.226 attackbots
Jan  8 23:39:11 eventyay sshd[28626]: Failed password for root from 222.186.173.226 port 62583 ssh2
Jan  8 23:39:24 eventyay sshd[28626]: error: maximum authentication attempts exceeded for root from 222.186.173.226 port 62583 ssh2 [preauth]
Jan  8 23:39:29 eventyay sshd[28629]: Failed password for root from 222.186.173.226 port 28982 ssh2
...
2020-01-09 06:42:16
217.61.121.48 attackspam
SASL PLAIN auth failed: ruser=...
2020-01-09 07:18:23
185.156.73.38 attackbotsspam
TCP Port Scanning
2020-01-09 06:41:15
37.252.85.69 attackspambots
firewall-block, port(s): 1433/tcp
2020-01-09 06:56:03
188.2.120.213 attackbots
Jan  8 22:09:54 vps670341 sshd[9403]: Invalid user test from 188.2.120.213 port 53372
2020-01-09 06:58:51
159.203.201.213 attackbots
8005/tcp 20358/tcp 22141/tcp...
[2019-11-08/2020-01-08]44pkt,38pt.(tcp),3pt.(udp)
2020-01-09 06:43:26
222.186.175.181 attackbotsspam
Jan  9 00:06:43 mail sshd\[30926\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.181  user=root
Jan  9 00:06:45 mail sshd\[30926\]: Failed password for root from 222.186.175.181 port 12782 ssh2
Jan  9 00:07:08 mail sshd\[30935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.181  user=root
Jan  9 00:07:11 mail sshd\[30935\]: Failed password for root from 222.186.175.181 port 62531 ssh2
Jan  9 00:07:14 mail sshd\[30935\]: Failed password for root from 222.186.175.181 port 62531 ssh2
...
2020-01-09 07:08:42
173.212.245.177 attack
st-nyc1-01 recorded 3 login violations from 173.212.245.177 and was blocked at 2020-01-08 23:14:34. 173.212.245.177 has been blocked on 20 previous occasions. 173.212.245.177's first attempt was recorded at 2020-01-08 18:00:15
2020-01-09 07:15:09
197.52.152.179 attackspam
Lines containing failures of 197.52.152.179
Jan  8 22:21:23 MAKserver05 sshd[7994]: Invalid user test from 197.52.152.179 port 50795
Jan  8 22:21:23 MAKserver05 sshd[7994]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.52.152.179 
Jan  8 22:21:25 MAKserver05 sshd[7994]: Failed password for invalid user test from 197.52.152.179 port 50795 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=197.52.152.179
2020-01-09 07:02:14
46.38.144.57 attack
Jan  8 23:56:38 relay postfix/smtpd\[31693\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 23:57:49 relay postfix/smtpd\[8294\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 23:58:03 relay postfix/smtpd\[31693\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 23:59:16 relay postfix/smtpd\[10968\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan  8 23:59:34 relay postfix/smtpd\[31693\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-09 07:14:52
31.27.38.242 attackbotsspam
Jan  8 23:51:42 MK-Soft-VM8 sshd[20212]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.27.38.242 
Jan  8 23:51:44 MK-Soft-VM8 sshd[20212]: Failed password for invalid user ftpuser from 31.27.38.242 port 49034 ssh2
...
2020-01-09 07:01:45
92.63.194.91 attackbotsspam
firewall-block, port(s): 1723/tcp
2020-01-09 07:07:35

Recently Reported IPs

37.0.8.221 169.229.251.219 169.229.0.168 148.66.19.106
35.196.217.244 192.241.220.40 192.241.221.38 45.143.203.88
169.229.251.255 169.229.252.182 169.229.252.223 169.229.253.49
169.229.254.90 131.161.8.205 52.66.210.247 159.65.50.70
186.215.100.34 39.98.203.186 220.203.8.38 40.81.141.96