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

;; QUESTION SECTION:
;137.226.42.161.			IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jun 25 14:11:11 CST 2022
;; MSG SIZE  rcvd: 107
Host info
161.42.226.137.in-addr.arpa domain name pointer eeltb161.llt.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
161.42.226.137.in-addr.arpa	name = eeltb161.llt.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
54.37.66.73 attackbots
Mar 28 19:54:44 santamaria sshd\[16488\]: Invalid user ypl from 54.37.66.73
Mar 28 19:54:44 santamaria sshd\[16488\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.66.73
Mar 28 19:54:46 santamaria sshd\[16488\]: Failed password for invalid user ypl from 54.37.66.73 port 56084 ssh2
...
2020-03-29 02:57:51
125.27.141.249 attack
SSH Brute Force
2020-03-29 02:34:49
159.203.142.91 attackbots
k+ssh-bruteforce
2020-03-29 02:42:54
106.12.150.188 attack
$f2bV_matches
2020-03-29 02:48:55
65.229.5.158 attackspambots
SSH Brute Force
2020-03-29 02:56:33
106.13.140.252 attackbots
5x Failed Password
2020-03-29 02:27:22
177.70.106.134 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-03-29 03:09:12
122.51.105.141 attackspam
SSH/22 MH Probe, BF, Hack -
2020-03-29 02:35:15
103.232.101.140 attackbotsspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-03-29 02:49:15
202.88.252.53 attackbotsspam
Mar 28 15:00:39 124388 sshd[20552]: Invalid user eco from 202.88.252.53 port 60804
Mar 28 15:00:39 124388 sshd[20552]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.88.252.53
Mar 28 15:00:39 124388 sshd[20552]: Invalid user eco from 202.88.252.53 port 60804
Mar 28 15:00:41 124388 sshd[20552]: Failed password for invalid user eco from 202.88.252.53 port 60804 ssh2
Mar 28 15:05:08 124388 sshd[20578]: Invalid user mlo from 202.88.252.53 port 8385
2020-03-29 02:38:01
95.181.131.153 attackbotsspam
$f2bV_matches
2020-03-29 02:50:34
58.228.159.253 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 39 - port: 3389 proto: TCP cat: Misc Attack
2020-03-29 02:57:29
196.219.94.254 attackspambots
SSH Brute Force
2020-03-29 02:38:37
185.53.88.39 attackbotsspam
ET SCAN Sipvicious User-Agent Detected (friendly-scanner) - port: 5060 proto: UDP cat: Attempted Information Leak
2020-03-29 03:08:38
184.22.118.168 attackbotsspam
SSH Brute Force
2020-03-29 02:39:41

Recently Reported IPs

220.87.164.54 137.226.42.196 83.23.250.35 83.43.130.186
14.146.93.239 85.138.29.222 137.226.54.119 108.64.193.106
111.220.174.123 111.248.22.215 137.226.65.207 137.226.66.24
137.226.66.48 137.226.66.55 137.226.66.66 137.226.72.51
137.226.72.85 137.226.72.128 137.226.72.146 137.226.72.165