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

;; QUESTION SECTION:
;137.226.56.113.			IN	A

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

;; Query time: 83 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 12 18:46:11 CST 2022
;; MSG SIZE  rcvd: 107
Host info
113.56.226.137.in-addr.arpa domain name pointer g3085-1.sht.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
113.56.226.137.in-addr.arpa	name = g3085-1.sht.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
125.161.107.154 attackbotsspam
20/5/6@08:00:31: FAIL: Alarm-Network address from=125.161.107.154
20/5/6@08:00:31: FAIL: Alarm-Network address from=125.161.107.154
...
2020-05-06 23:13:15
61.227.136.145 attack
20/5/6@08:00:09: FAIL: Alarm-Network address from=61.227.136.145
20/5/6@08:00:09: FAIL: Alarm-Network address from=61.227.136.145
...
2020-05-06 23:46:37
112.85.42.173 attack
Fail2Ban Ban Triggered
2020-05-06 23:11:29
209.222.101.41 attackbots
May  6 17:26:03 mail kernel: [784380.525605] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=209.222.101.41 DST=77.73.69.240 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=42156 PROTO=TCP SPT=56528 DPT=29634 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2020-05-06 23:37:15
212.237.37.205 attack
SSH bruteforce
2020-05-06 23:19:19
104.215.197.210 attackspam
$f2bV_matches
2020-05-06 23:53:45
106.13.31.119 attackbots
May  6 15:21:31 piServer sshd[9132]: Failed password for root from 106.13.31.119 port 36934 ssh2
May  6 15:26:33 piServer sshd[9482]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.31.119 
May  6 15:26:35 piServer sshd[9482]: Failed password for invalid user qip from 106.13.31.119 port 40190 ssh2
...
2020-05-06 23:50:50
93.49.11.206 attack
May  6 20:25:58 gw1 sshd[9674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.49.11.206
May  6 20:26:00 gw1 sshd[9674]: Failed password for invalid user rdi from 93.49.11.206 port 39503 ssh2
...
2020-05-06 23:26:39
219.91.66.141 attack
trying to access non-authorized port
2020-05-06 23:25:01
185.173.35.53 attackspambots
firewall-block, port(s): 2483/tcp
2020-05-06 23:35:19
46.101.174.188 attackbots
...
2020-05-06 23:55:03
104.248.43.155 attack
firewall-block, port(s): 17224/tcp
2020-05-06 23:46:18
178.71.184.252 attackspam
0,30-04/31 [bc15/m21] PostRequest-Spammer scoring: essen
2020-05-06 23:47:42
194.247.178.11 attackspambots
Unauthorized connection attempt from IP address 194.247.178.11 on Port 445(SMB)
2020-05-06 23:14:29
178.62.224.217 attack
firewall-block, port(s): 17138/tcp
2020-05-06 23:38:28

Recently Reported IPs

137.226.54.134 173.234.225.236 137.226.54.205 137.226.54.30
137.226.57.91 137.226.56.75 137.226.55.7 137.226.56.204
137.226.55.228 133.130.176.103 137.226.34.215 137.226.32.97
137.226.115.48 137.226.35.99 176.222.162.226 172.245.92.115
188.143.233.80 178.137.16.99 178.137.16.161 137.226.54.111