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

;; QUESTION SECTION:
;137.226.104.4.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 23 05:39:42 CST 2022
;; MSG SIZE  rcvd: 106
Host info
4.104.226.137.in-addr.arpa domain name pointer d-ew-st01.devlef.campus.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
4.104.226.137.in-addr.arpa	name = d-ew-st01.devlef.campus.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.216.128.197 attack
31.12.2019 06:49:09 - Login Fail on hMailserver 
Detected by ELinOX-hMail-A2F
2019-12-31 14:28:31
209.97.183.237 attackspam
209.97.183.237 - - [31/Dec/2019:06:30:00 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
209.97.183.237 - - [31/Dec/2019:06:30:00 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-12-31 14:42:56
46.233.10.106 attack
invalid login attempt (rwilliams)
2019-12-31 14:09:51
80.250.217.50 attack
Dec 31 07:55:35 sd-53420 sshd\[20243\]: Invalid user brashear from 80.250.217.50
Dec 31 07:55:35 sd-53420 sshd\[20243\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.250.217.50
Dec 31 07:55:37 sd-53420 sshd\[20243\]: Failed password for invalid user brashear from 80.250.217.50 port 26104 ssh2
Dec 31 07:57:51 sd-53420 sshd\[21097\]: Invalid user bbbbb from 80.250.217.50
Dec 31 07:57:51 sd-53420 sshd\[21097\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.250.217.50
...
2019-12-31 14:58:59
218.92.0.175 attackspam
SSHScan
2019-12-31 14:42:09
220.94.12.47 attackspambots
Port Scan
2019-12-31 15:01:35
94.141.102.178 attackspambots
Unauthorized connection attempt detected from IP address 94.141.102.178 to port 445
2019-12-31 14:14:44
160.119.128.102 attackbots
Automatic report - XMLRPC Attack
2019-12-31 14:51:23
78.128.113.166 attackspam
20 attempts against mh_ha-misbehave-ban on oak.magehost.pro
2019-12-31 14:54:15
66.240.236.119 attackspambots
Dec 31 07:29:49 debian-2gb-nbg1-2 kernel: \[33124.626754\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=66.240.236.119 DST=195.201.40.59 LEN=44 TOS=0x10 PREC=0x00 TTL=110 ID=32944 PROTO=TCP SPT=20012 DPT=9443 WINDOW=33348 RES=0x00 SYN URGP=0
2019-12-31 14:52:47
112.78.168.66 attackspambots
Fail2Ban Ban Triggered
2019-12-31 14:43:31
45.136.108.85 attack
ssh failed login
2019-12-31 14:28:04
106.12.54.182 attack
Automatic report - Banned IP Access
2019-12-31 14:49:13
82.178.234.69 attack
12/31/2019-05:55:25.724621 82.178.234.69 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-31 14:10:19
46.197.11.13 attack
[Aegis] @ 2019-12-31 06:23:10  0000 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-12-31 14:29:45

Recently Reported IPs

137.226.196.1 114.33.180.181 113.240.23.123 169.229.174.201
114.96.88.121 169.229.167.212 137.226.224.118 137.226.137.179
137.226.51.169 137.226.108.124 114.99.4.142 137.226.221.121
137.226.55.84 137.226.179.185 184.105.247.209 137.226.117.0
137.226.66.175 137.226.169.71 137.226.179.101 137.226.160.192