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: Aachen

Region: North Rhine-Westphalia

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

;; QUESTION SECTION:
;137.226.197.42.			IN	A

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

;; Query time: 161 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 29 12:27:19 CST 2022
;; MSG SIZE  rcvd: 107
Host info
42.197.226.137.in-addr.arpa domain name pointer mtz-137-226-197-42.pmi.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.197.226.137.in-addr.arpa	name = mtz-137-226-197-42.pmi.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
123.20.22.206 attack
Unauthorized connection attempt detected from IP address 123.20.22.206 to port 445
2019-12-17 04:06:03
222.186.175.167 attackbotsspam
Dec 16 10:25:33 hanapaa sshd\[27599\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167  user=root
Dec 16 10:25:35 hanapaa sshd\[27599\]: Failed password for root from 222.186.175.167 port 36074 ssh2
Dec 16 10:25:52 hanapaa sshd\[27627\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167  user=root
Dec 16 10:25:54 hanapaa sshd\[27627\]: Failed password for root from 222.186.175.167 port 57178 ssh2
Dec 16 10:26:13 hanapaa sshd\[27665\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167  user=root
2019-12-17 04:34:58
89.248.173.102 attackbotsspam
B: f2b ssh aggressive 3x
2019-12-17 04:15:10
61.12.38.162 attackbotsspam
2019-12-16T16:28:48.126232abusebot-7.cloudsearch.cf sshd\[731\]: Invalid user viste from 61.12.38.162 port 44842
2019-12-16T16:28:48.132570abusebot-7.cloudsearch.cf sshd\[731\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.12.38.162
2019-12-16T16:28:50.032064abusebot-7.cloudsearch.cf sshd\[731\]: Failed password for invalid user viste from 61.12.38.162 port 44842 ssh2
2019-12-16T16:34:59.207883abusebot-7.cloudsearch.cf sshd\[830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.12.38.162  user=root
2019-12-17 04:03:34
159.65.132.170 attackspam
Dec 16 09:44:37 php1 sshd\[21035\]: Invalid user dub from 159.65.132.170
Dec 16 09:44:37 php1 sshd\[21035\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.132.170
Dec 16 09:44:38 php1 sshd\[21035\]: Failed password for invalid user dub from 159.65.132.170 port 58862 ssh2
Dec 16 09:50:31 php1 sshd\[21935\]: Invalid user mhwang from 159.65.132.170
Dec 16 09:50:31 php1 sshd\[21935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.132.170
2019-12-17 04:14:54
45.6.72.17 attackbots
SSH Brute Force
2019-12-17 04:28:07
83.159.39.50 attackspambots
Attempted WordPress login: "GET /wp-login.php"
2019-12-17 04:24:00
106.13.7.186 attackspam
k+ssh-bruteforce
2019-12-17 04:31:50
178.128.221.162 attackspam
Dec 16 16:10:45 legacy sshd[2830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.221.162
Dec 16 16:10:47 legacy sshd[2830]: Failed password for invalid user bryars from 178.128.221.162 port 40144 ssh2
Dec 16 16:17:24 legacy sshd[3122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.221.162
...
2019-12-17 04:21:15
51.68.122.216 attackbots
Dec 16 19:17:15 srv01 sshd[6997]: Invalid user espina from 51.68.122.216 port 41592
Dec 16 19:17:15 srv01 sshd[6997]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.122.216
Dec 16 19:17:15 srv01 sshd[6997]: Invalid user espina from 51.68.122.216 port 41592
Dec 16 19:17:18 srv01 sshd[6997]: Failed password for invalid user espina from 51.68.122.216 port 41592 ssh2
Dec 16 19:22:14 srv01 sshd[7480]: Invalid user husum from 51.68.122.216 port 48824
...
2019-12-17 04:16:36
200.38.167.135 attackbotsspam
Dec 16 21:00:09 grey postfix/smtpd\[24965\]: NOQUEUE: reject: RCPT from smptsvr.inr.gob.mx\[200.38.167.135\]: 554 5.7.1 Service unavailable\; Client host \[200.38.167.135\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[200.38.167.135\]\; from=\ to=\ proto=ESMTP helo=\
...
2019-12-17 04:21:31
116.102.220.134 attackspam
Unauthorized connection attempt detected from IP address 116.102.220.134 to port 445
2019-12-17 04:09:42
154.49.211.67 attack
Dec 16 17:32:07 markkoudstaal sshd[15358]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.49.211.67
Dec 16 17:32:09 markkoudstaal sshd[15358]: Failed password for invalid user lisa from 154.49.211.67 port 35524 ssh2
Dec 16 17:37:41 markkoudstaal sshd[15934]: Failed password for root from 154.49.211.67 port 42682 ssh2
2019-12-17 04:08:08
165.22.57.25 attack
Dec 16 17:46:11 server sshd\[10919\]: Invalid user host from 165.22.57.25
Dec 16 17:46:11 server sshd\[10919\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.57.25 
Dec 16 17:46:13 server sshd\[10919\]: Failed password for invalid user host from 165.22.57.25 port 50974 ssh2
Dec 16 17:54:22 server sshd\[13094\]: Invalid user grenske from 165.22.57.25
Dec 16 17:54:22 server sshd\[13094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.57.25 
...
2019-12-17 04:02:40
80.211.95.201 attackspam
SSH Bruteforce attack
2019-12-17 04:06:17

Recently Reported IPs

137.226.202.130 137.226.185.246 137.226.239.182 47.189.229.99
137.226.239.65 137.226.157.140 137.226.239.83 137.226.247.85
137.226.241.233 137.226.237.22 137.226.156.211 137.226.32.76
137.226.28.189 137.226.108.15 137.226.58.161 137.226.141.190
106.248.141.195 164.92.106.112 137.226.221.103 110.77.153.59